I have two conflicting state changes being done from an event handler. I would like the first to be done, trigger recompose, and then the second (no-longer conflicting, since it would be based on the newly updated state) to be done. This isn't what happens, is there a way to force it? Note that these event handlers are passed in. I could potentially force recomposition between them, but that would be expensive when the event handlers don't need it. Minimal example in :thread-please:

Question about recomposition with

List

and

SnapshotStateList

Using

List

instead of

SnapshotStateList

with

items.forEachIndexed

causes recomposition of all the composables. For example in the below code when I click

Button A

it calls a function in viewmodel which increments the

progressState

by 10. This state change should recompose only the

A

composable but it causes recomposition of

B

as well. Any idea why ? Example in the thread :thread-please:

https://developer.android.com/jetpack/androidx/releases/navigation#2.4.0-alpha07 Got to wait before upgrading to this dependency to use alongside accompanist, despite all the great bug fixes. It doesn't play nice with accompanist AnimatedNavhost(), when trying to use it an error occurs

java.lang.ClassCastException: java.util.ArrayList cannot be cast to java.util.Set
        at com.google.accompanist.navigation.animation.AnimatedNavHostKt.AnimatedNavHost$lambda-3(AnimatedNavHost.kt:323)
        at com.google.accompanist.navigation.animation.AnimatedNavHostKt.AnimatedNavHost(AnimatedNavHost.kt:158)
        at com.google.accompanist.navigation.animation.AnimatedNavHostKt.AnimatedNavHost(AnimatedNavHost.kt:85)

has this been fixed in the latest navigation update? https://issuetracker.google.com/issues/194313238

navigation-compose 2.4.0-alpha05 does not keep a subgraph’s BackStackEntry until the transition animation completes

Hey! Maybe someone has encountered Skia crashes in production when running Compose. Stacktrace in thread 👇🏻

TextField(
        value = feedContent.observeAsState().value ?: "",
        onValueChange = {
            if (it.length <= 200) {
                feedContent.value = it
            }
        },
        maxLines = 4,
        colors = textFieldColors(
                textColor = colorResource(id = R.color.color_22BE8C),
                cursorColor = colorResource(id = R.color.colorPrimary),
                backgroundColor = colorResource(id = R.color.color_f1f3f7),
                focusedIndicatorColor = Color.Transparent,
                unfocusedIndicatorColor = Color.Transparent,
                disabledIndicatorColor = Color.Transparent
        ),
        shape = RoundedCornerShape(6.dp),
        placeholder = {
            Text(text = stringResource(id = R.string.feedback_input_desc),
                    modifier = Modifier.wrapContentSize(),
                    color = colorResource(id = R.color.color_BBBBC3), fontSize = 14.sp)
        },
        modifier = Modifier
                .fillMaxWidth()
                .wrapContentHeight(align = <http://Alignment.Top|Alignment.Top>)
                .padding(top = 20.dp)
                .background(Color(0xF1F3F7), RoundedCornerShape(6.dp)),
)

why show the textcolor is colorPrimary????

What could be a reason that a LazyColumn produces this crash?

java.lang.ArrayIndexOutOfBoundsException: length=32; index=32
        at androidx.compose.runtime.collection.IdentityArrayMap.remove(IdentityArrayMap.kt:100)
        ...

Do you guys keep/take dp values from R.dimen still?

This message was deleted.

Hi, it is possible to use Flow with Jetpack Compose?

Good day everyone! This doesn’t work. Details are in the thread below

viewModel::onExampleButtonClicked

Does

fillMaxSize

not work if the container is scrollable?

This

Text

with

maxLines = 1

and

overflow = TextOverflow.Ellipsis

breaks before a new word, causing the menu item to not take up the full available width. I there was no space behind the last "a", the item would have a larger width. My question is, how can I let this

Text

wrap in the middle of words instead? I tried

softWrap = false

but it has no effect

❓ Question: [Navigation Compose]: How can i get number of items in the backstack using

NavHostController

?

I’m trying to disable autofill on compose for android. I’m using a

OutlinedTextField

, and i’ve set it up with

PasswordVisualTransformation

. Autofill appears shortly after typing a few characters. Any hints on how to disable the built-in autofill? 😅 Thanks in advance!

I am getting the following error on build:

e: This version (1.0.0-beta07) of the Compose Compiler requires Kotlin version 1.4.32 but you appear to be using Kotlin version 1.5.21 which is not known to be compatible.  Please fix your configuration (or `suppressKotlinVersionCompatibilityCheck` but don't say I didn't warn you!).

But I am using compose 1.0.1 and the only place that uses beta is

androidx.constraintlayout:constraintlayout-compose:1.0.0-beta02

which itself is beta02 not beta07, I am not sure if internally it uses compose compiler beta07. How do I resolve this issue.??

Is there any mechanism like

remember

but instead of recalculating if dependencies change, it recalculates if a given predicate is true? My use case is I have some UI content within an

AnimatedVisibility

block, where

visible = uiState is InitialUiState

. (My UI state is a sealed class with subtypes we can call

InitialUiState

and

SecondaryUiState

.) Some of the UI content I'm animating depends on a property contained within

InitialUiState

, but not

SecondaryUiState

. So when it's animating out of visibility, my

uiState

no longer contains the data needed in order to render the UI. I can wrap the content in

if (uiState is InitialUiState)

, but then the content just disappears instead of animating out. My thought is I need to memoize the most recent

InitialUiState

value, using something like

val initialUiState = rememberUnless(uiState is InitialUiState) { uiState as? InitialUiState }

, so that we can access the data contained within the last

InitialUiState

, even when the current value of

uiState

is a

SecondaryUiState

. In this example it would recalculate on every composition where

uiState is InitialUiState

, but "remember" and return the previous calculation otherwise.

What's everyone's thoughts on passing in your viewModel to your top level composable VS passing in just your uiState? I'm leaning towards passing in the uiState since it seems that's all you need to preview/test but I was wondering if there's a best practice we should follow and why?

If I have a column with several components in it, how do I make one of those components always be at the bottom (specifically a FAB button)

So this question has been asked like a zillion times, but let me ask it again, what's up with

androidx.compose.ui.tooling.PreviewActivity is not an Activity subclass or alias

.?? I am on the latest stable version of everything, • Compose 1.0.1 • AGP 7.0.2 • Kotlin 1.5.21 • Android Studio Arctic Fox Patch 1 ...and still this issue is coming. What's up with that. And how do I fix it.?? Its so annoying. And why does making a duplication Run Configuration of the same just works perfectly fine.??

Compose noob here, i'm trying to use

keys

to avoid recomposition of previously composed ones but can't seem to get it to work. Displaying a list with items and a button to shuffle the list item but all items are composed again (logging via

SideEffect

)

I have a lazy column with a gradient background, and I want the gradient to be the entire height. BUT after I start scrolling I want to gradient to scroll up/off of the screen. Any Ideas on how to implement? I currently have a Box { GradientBackground() LazyColumn() } but the Gradient (of course) doesn't move up. Is there anything Col or LazyCol provide for this sort of thing? Kind of like a "first page background", and then a background for everything below the device height?

Is it possible to do something like that in the latest version of Compose?

Hello everyone. Does someone know what will be the plan moving for supporting new versions of the Kotlin compiler? Will Compose always require explicit support for any new compiler version?

Just to clarify: If I log something during recomposition of the top-level function of my Compose app, and that log occurs every 16 milliseconds, then one of the arguments to the top-level function has "changed" according to Compose?

i want render diff view with data but when use state it not change like this:

val state: MutableList<String>? by imageList.observeAsState(mutableListOf())
if (state.isNullOrEmpty()) {
    feedbackPlaceView(addImgClick)
} else {
    state?.forEachIndexed { listIndex, s ->

Hello is there a a configuration to lock compose at horizontal orientation?

Is there any further plan to improve LazyColumn performance?