If you want to join my #androidui channel please do so - I am looking for new people that are eager to share their ui to join. Cheers,

Is it possible to use Compose without an AppCompatActivity, and just

android.app.Activity

? I see that it requires a

ViewTreeLifecycleOwner

, which can be instantiated and set manually. However the

ViewTreeSavedStateRegistryOwner

cannot be instantiated, so it must be used with an AppCompatActivity, right? Is there any way for me to get a

ViewTreeSavedStateRegistryOwner

without AppCompatActivity or get Compose (specifically

ComposeView

, which checks for these) to work?

Hi all, I'm trying to import a library with Jetpack compose

1.0.0-beta01

(Android Gradle plugin 7.0.0-alpha09) into an app that doesn't have jetpack compose and android gradle plugin 4.1.0. I'm getting an error

java.lang.NoClassDefFoundError: Failed resolution of: Landroidx/compose/runtime/internal/ComposableLambdaKt;

when I try to open up my compose views from the library. Has anyone seen this kind of issue before / know a fix? I thought compose could be used in a library only and then not be required for the app (my client app has product requirements limiting it from updating the AGP / going to compose).

Hey folks, is there an easy way to say tell a Button to use secondary colours without having to go through and define all the properties for ButtonColors ?

Is it a known issue that TextField icons and text are impossible to align to a common baseline, or am I missing an obvious API here? This icon is centered correctly, but the text is way too far up. I’ve seen the same thing on all the submissions to the Compose Challenge that I came across on Twitter, so I’m wondering if it might be a problem with the custom font

Hey folks, I am using Compose version

1.0.0-beta02

and

MaterialTheme.colors.isLight

does not change when we give light and dark themes with a Boolean mutable state. It was working before. Is there anyone else with the same situation.

Is there any difference between usage of remember below ?

@Composable
fun ClubItem(club: Club,
             selectedClubs: List<Club> = emptyList(),
             onItemClicked: (Club) -> Unit) {
    val isSelected by remember { derivedStateOf { selectedClubs.contains(club) } }
}

@Composable
fun ClubItem(club: Club,
             selectedClubs: List<Club> = emptyList(),
             onItemClicked: (Club) -> Unit) {
    val isSelected by remember { mutableStateOf(selectedClubs.contains(club)) }
}

Is there a difference between

fillMaxSize()

and using

fillMaxHeight().fillMaxWidth()

?

Hi. Dummy question: This week dev challenge asks to create a typography in CAPS, is there a way to do that, without set the

"".toUpperCase()

?

This message was deleted.

Does anyone experience random crashes on a compose app? My app crashes randomly like I have my app running on the emulator and then I switch to Android Studio to write some code, then when I switch back to the emulator I find out the app has been crashed already and there's no error in logcat. Sometimes it crashes while navigating the app too. This might be an issue with the emulator and not compose related but I've only experienced it in compose apps.

ScrollableColumn or ScrollableRow function is delete? https://developer.android.com/reference/kotlin/androidx/ui/foundation/package-summary#scrollablerow

I have a Row with elements with different heights. How can I say, that one row element should have the max. available height of the Row (i.e. the maximum of inner element heights)? Something like "matchParentHeight".

Row {
    Column() { ... }
    Column(Modifier.matchParentHeight()) { ... }
}

Hi, I'm learning compose and I come from a background where I like the redux way of doing things. So I normally would have an immutable data class describing the state of the whole screen, and this up-to-date state would be exposed through StateFlow to the view side. So I've tried to keep doing that here and I have something like this

@Composable
fun HelloScreen(helloViewModel: HelloViewModel = viewModel()) {
    val state: HelloState by helloViewModel.stateFlow.collectAsState(initialState)
    Column {
        Text(state.title)
        SomeStatelessComponent(state.componentValue)
        SomeOtherStatelessComponent(state.otherComponentValue)
        ...
    }
}

The idea is that every composable used in HelloScreen are simply stateless composables. My worry is that this won't work out great if compose simply does a reference check (===) instead of an equals to check if it should recompose these stateless composables. If compose simply does a reference check, I see three ways out of this: • Wrapping every object in this state class in mutableStateOf and adjust the reducer on the viewmodel side -> seems terrible, does this even work? • Having a stateflow per state value -> seems clunky if your screen has a lot of state properties. • Orrr find a way to selectively "subscribe" to the stateFlow properties, like

stateFlow.map { state -> state.componentValue }.distinctUntilChanged()

Is this okay? I'm up for other ideas

frames skipping a lot with simple textfield and remember

Hello, is there a way how to absolutely position child composable within

Box

? I have a code like this

@Preview("Positioning", widthDp = 300, heightDp = 300)
@Composable
fun Positioning() {
    Box(
        modifier = Modifier.size(300.dp)
            .background(Color.Blue)
    ) {
        Box(
            modifier = Modifier.size(20.dp)
                .background(Color.Red)
                .absoluteOffset(20.dp, 20.dp)
        )
    }
}

and I’d like to position inner

Box

but the result is not positioned. I know that it does not make sense probably to apply offset to

Modifier

of inner

Box

because I’d need to affect outer

Box

somehow but I did not find a way how to position just a single child. I know I can achieve it easily with Canvas drawing but I’m just thinking what if I’d want to position some other

Composable

. Thanks

Hi! I’m trying to build a row similar to this one(img below): If I use two harcoded strings it works just fine, but in my case, I obtain the first string from the activity intent and the second one from string resources. I don’t get why, when I do so, it breaks the UI. Only the first string is shown, and the rest of the elements of the screen move down a bit. I’m doing it this way because the second string should be clickable and in a different colour. There are probably different ways of doing this, but I can’t see what I am doing wrong here.

@Composable
  fun Subtitle(modifier: Modifier = Modifier, first: String, second: String) {
    Row(modifier = modifier.padding(8.dp)) {
      Text(
        text = first,
        color = colorResource(id = R.color.textLight),
        fontSize = 16.sp
      )
      Text(
        modifier = modifier.padding(start = 2.dp),
        text = second,
        color = colorResource(id = R.color.textBrand),
        fontSize = 16.sp
      )
    }
  }

Subtitle(first = args.summary, second = stringResource(R.string.general_more_info))

Is it possible to apply different styles (e.g. colour) to each word of a given String? I have turned the String into a list of words like this:

val convertedString = textState.value.text.splitToSequence(' ')
        .filter { it.isNotBlank() }
        .toList()

But I can't find how to differentiate the words to decorate them differently:

Text(textState.value.text,  style = TextStyle(color = listOfColors.random()))

hey I'm building an editor toolbar so I need to pass

MaterialTheme.Typography

through

data class

property

and it's not possible because the

MaterialTheme.Typography

is a

Composable

so we can't use it in

non-composable

. and now the question is how can I achieve that? the code is in thread to take less space.

I'm using graphicsLayer to update the alpha of composable while scrolling. But it causing performance issue. Is it a know issue?

I just wanted to sense check my usage of

BoxWithConstraints

Feels I might need to use a Layout/SubcomposeLayout instead, but I’m not sure I’m using the maxWidth and maxHeight to calculate sizes and positions for items on a “grid”

staticAmbientOf

as well

I have a noob contributor question. Trying to play with the compose codebase to debug an issue I’ve found. In order to reproduce it, I’m trying to add

dev.chrisbanes.accompanist:accompanist-insets:0.6.2

to

:compose:foundation:foundation-layout:build.gradle

. I’ve added it to both

androidTestImplementation

for non-MPP builds, and to

androidAndroidTest.dependencies

for MPP builds. After a Gradle sync, I still can’t reference accompanist insets in

BoxTest.kt

. What am I missing?

Is there a way to disable "elevation overlays" for darkColors theme?

My activity is just made up of MyComposablePage but it still has the default Material colors (purple) even though in the Manifest I set the app theme to my typical app theme where the primary color is green. I would have thought that that should work, but it doesn't? Should I file a bug or is that working as expected and I need to pass the theme into my composable page?

Hi y'all. What's the guidance for picking

mutableStateListOf<Item>()

vs

mutableStateOf<List<Item>>()

? Trying to assess stability/performance in the case of a

List

(size ~200) that will undergo random removals/insertions (that will be either displayed in a

LazyColumn

or

LazyGrid

)

I have a TransformableState that is used for zooming and moving an image around freely. How would I optimally measure the image location so it does not get moved outside of the window and change the pan/offsets of the transformableState so this does not happen. I have the Modifier.onGloballyPositioned which gives me the LayoutCoordinates. How can I get the Window size to calculate by how much i need to change the offsets (or are there better approaches?)

I'm trying to fully understand

composed

modifier that is used for custom stateful modifiers. My first question is what are the limitations around it? It's a compose function so it lets me call any other composable function that may or may not emit widgets. For example it makes sense to use

remember

but it's a little strange calling

Box

.

Is try/catch supported in

@Composables

now? I tried using

runCatching

and I got a weird error where the result was interpreted as a

T

(and not a

Result<T>

, see screenshot the debugger sees two types for the same lvalue ?!?). I ended up using try/catch and now it's all working but searching the backlog of this channel (https://kotlinlang.slack.com/archives/CJLTWPH7S/p1603737209131700), it looks like this might be dangerous?