I'm working with

SnapshotStateMap<String, Any>

and storing the value in a state object:

// viewmodel content

private val state: SnapshotStateMap<String, Any> = mutableStateMapOf()
var myState by mutableStateOf(StateObject(state.getValue("key")))

@Immutable
data class StateObject(val value: Any)

I'm changing the values by bubbling up a

onValueChange

event that accesses

state

like state["key"] = newValue. But when I use for example a

Slider

composable and

onValueChange

is triggered, the Slider does not reflect the change, although I can print the new values. I guess storing the value in a state object as intermediate step is the problem. Is this intended or do I miss something here?

Is there any tutorial or guide how to draw UML diagram for

Composable

component , which is helpful to visualize relationships between different UI elements

Can someone review this snippet of code to tell me whether or not a

remember{}

is needed? Code in thread

Compose previews. Top or bottom of the file? I can think of reasons for both ways.

Hello, Is there a way to handle the long press deletion of a text in a

TextField

- it feels like previously was the default behaviour, but I think with Compose it is not :?

Is there a clever way to do lazy initiation of variables within a composable scope?

An android lint to make

@Preview

functions private to avoid polluting code completion might be useful?!

Good morning and Happy Google I/O day to everyone! I have a question about the Accompanist WebView. I think this may be an issue, but wanted to check before I logged it. Details in 🧵

Hello, I have 2 options to consider for Image Loading In Compose 1. Glide 2. Coil (a new boy in Town) Almost both share common features like 1. Both has Request Options functionality 2. Both give placeholder, error, success callback for Image 3. Both has Transitions & Transformations Support 4. Coil has extra AsyncImage Can anyone share performance insights with their experience ?? Only Glide has big size as compare to Coil Can anyone share experience on which we should consider at first place for using with Jetpack Compose ??? It would be of great help.Thanks

Hi all! I need to scroll on a component even screen has enough space, is that possible? I’ve tried the below code, it works well if the screen is small but it doesn’t work on if there is enough space to show all content. Please see the thread

Hello! Where can i get information for compose material icons and materialIconsExtended? Some kind of table with name and icon image?

"In Android Studio Electric Eel, you can use Live Edit to see the effect of updates to composables in real time. Live Edit updates Compose Preview and deploys code changes to an emulator or device. You don't have to wait for builds or deployments to be completed, so you can make faster progress in the creation of your app’s experience." https://developer.android.com/studio/preview/features#live_edit

patiently waits for

accompanist v0.24.8-beta

to drop 🙃

I'm right here waiting as well 😆

https://youtu.be/qBkyU1TJKDg?t=2529▾

Holy f***ing shit

What is the difference between nesting a

Column

inside of a

Surface

as opposed to adding the

.background(color = MaterialTheme.colors.surface)

modifier to the

Column

? Which one would you consider better practice?

is it possible in compose redraw parent, but not redraw a child? For example i want single point for bottom sheet showing - and all app content must be placed inside BottomSheet content. But there can be different bottom sheets. And here i meet the need to change wrapping view (bottom sheet) without changing its content (the app) Can i do that somehow? I can just have single bottom sheet and change it layout, but it isnt looks good

Has anyone has problem with the new live edit? I can’t seem to enable it even after upgrading to compose 1.2.0-beta01. After every change it shows out of date on the preview and I have to manually refresh it

I seem to be having a weird issue where compose preview shows wrong resources. The preview shows a different drawable or different string than what is referenced in the code. As if something was messing up resource IDs in previews.

Why does this keeps recomposing

Button

slot's content and printing "recomposing"?

MaterialTheme {
  val handler = { _: TextLayoutResult -> }
  MyButton(handler)
}

@Composable
fun MyButton(handler: (TextLayoutResult) -> Unit) {
  val state by flowOf("two", "three").collectAsState("one")
  Button(onClick = {}, enabled = state == "two") {
    println("recomposing content")
    Text(text = "Button", onTextLayout = handler)
  }
}

If I remove "handler" parameter recomposition happens only once. Is there a way to somehow mark "handler" as stable?

Lets say we have a main screen with a

Scaffold

.The Scaffold has a

BottomNavigation

and a

TopAppBar

. Navigating between the child screens means switching the content of the Scaffold. How can I have different TopBar actions on each screen? Do I have to drop the TopAppBar of the main screen and let the child screens have its own Scaffold with TopAppBar ? Another possibility I'm aware of would be to pass down the related TopBar composable and switch it on screen change like I do it with the screen content?

Hi all. So i’m using Kover with the IntelliJ coverage engine, but i’m still getting a lack of branch coverage despite actually covering all the branch conditions in my function. It seems pretty consistent that all the opening and closing braces on a Composable function are marked this way. As a result, i’m missing. a bunch of branches in my overall coverage number. I thought the intellij engine was supposed to handle this sort of stuff better than jacoco?

I’ve a

LazyRow

where the items can have different sizes, as it’s the last composable on the bottom of the screen, if when scrolling the user scrolls to a smaller item than the ones displayed first the screen moves up, which makes it seems weird. My question: is there a way to set the

height

of a

LazyRow

to be of its tallest item?

This message was deleted.

Regarding hybrid testing. I could not find much information about testing espresso/compose mixed tests however did find some information relating to

createEmptyComposeRule()

however in practice using it with espresso tests with

ActivityScenario

based tests has issues with idling resource timeout. I found this repo that demonstrates the issue https://github.com/Maksim-Novikov/ComposeUiTestsBug (check the only

andoridTest

test there) I am not sure the source of this repo but a github community member posted it I guess however it demonstrates a workaround for my exact issue. My question is anyone using this approach and is there an official bug or something raised regarding this and the workaround? I can’t find anything 😞

I’m trying to use Compose instrumented tests to check that moving a discrete slider (with integer values) causes its associated text node to display the current slider value. I make the movement using

performTouchInput

and check the text with

hasText

. The way I devised to move the slider doesn’t work for all ranges, so I’m looking for suggestions for the best (correct) way to move it. (See 🧵 for details.)

Is there some nice documentation about animation as UI/UX like what animation spec convey what intent and things like that? Compose makes it easy to do many things, but as non designer there's so many options that I have no idea where to start.

Is there a good way to measure time to UI in compose? Meaning, can I measure how long it takes to fully render a UI?

Anyone? It's a critical issue, if on destroy isn't called: • Can't set result to previous screens • Can't clear resources properly if using that lifecycle callback • View models never call onCleared https://kotlinlang.slack.com/archives/CJLTWPH7S/p1652357807849139