How can I separate items in a LazyVerticalGrid with Dividers? Adding a horizontal line between each row is easy but I don't know how to separate the columns with vertical lines. Using a Box with a border doesn't work well because the start/end borders add up.

If an item inside a LazyList has several sub-items, does it make any difference if I use a key(stableKey){} when rendering them in terms of it recomposing less if only other sub-items are changed?

In compose, can we get width dynamically? For example I do have a Row with fillMaxWidth and in the elements I have two Box inside row to which I want to provide 50%-50% width of parent Row. If yes, how can I achieve it?

I get this error when navigating to a subscreen in the app after updating to compose 1.1.0-beta04:

java.lang.IllegalStateException: Place was called on a node which was placed already

What does that mean and how can I fix this?

So i’m trying to use the “dialog” feature on the navigation component. I’ve got things working mostly as i want, except for the handling of the back button. The back button should basically dismiss the dialog, which it does. However, i also want to run some code to insert a log statement when that happens. You can do this with the normal “Dialog” composable, via the

onDismissRequest

parameter. However, that seems to be missing from the navComponent.

Is it possible to have a screen that is floating over other screens, kinda like a Full Screen Dialog? I'm not looking for a modification of a

Dialog

but something more low level, simply a screen that overlays another screen

i'm using the

HorizontalPager

from the accompanist library with a content padding , but when swiping to the last item/page and do a "fast" swipe the previous items seems to disappear, this only seems to happen with a fast swipe move (maybe some overshoot swing animation?) ``````

How can i set the drawerContent width in

Scaffold

?

What is the right way to build a Row of children, where all children, except the last one, are left-aligned, and the last one is right-aligned?

What does r8 do to Compose Lambdas that allow such large optimizations for compose?

Is there any known issue in Jetpack Compose Navigation where the back gesture or certain screen taps can cause the entire Compose hierarchy to become non-interactable? We’re seeing, especially with the back gesture enabled instead of 3 button mode, that making the back gesture causes the whole Compose view we return to to be disconnected from all listeners and not interactive. If we back out again then everything works. What’s especially strange is that pressing the Close button to call navController.popBackStack() in a clickable callback doesn’t cause this issue, but that overriding the back behavior with a BackHandler to do the exact same thing does cause the issue. I do wonder if the cause is in any way related to the fact that we’re using Jetpack Navigation on some top-level screens and Jetpack Compose Navigation locally within certain sections of the app. Any thoughts? We’re pretty stumped right now. Compose version is 1.1.0-alpha03 with Accompanist 0.21.3-beta. We’re also using bottom sheets from Navigation-Material on some screens.

Do we have to do anything to enable auto-fill on text fields? I have my types setup as email and password, but my password manager doesn't prompt me with auto-fill at all, while my view based version of this screen does indeed prompt me.

Hi all, when using

akka persistence durable state query

what is the best way to store offset and to always start reading states from the latest

offset

stored

Is there any other way to have a

viewModel

scoped to a navigation destination than using

hiltViewModel

?

I got strange behavior (it doesn't snap pages) on accompanist view pager interact. On the video at first i try swipe pages, then i use control to change pages, then swipe with fingers again. In case when I use pager control then pages snaps correctly, but when i use finger pager works like recycler view. Pager control is not the problem source, because i commented it and behavior haven't changed. Do you have any ideas what can lead that behavor? Or maybe somewho met same behavior?

i am using accompanist view pager is there any way to set offscreenPageLimit like normal viewpager?

So im trying to save a canvis as as a png on desk top

Compose doc's explaining dependency tree scope to those that already can't explain scoping. #thermoSiphon

I am setting up a few pages using the

pager

+

pager-indicator

accompanist libraries. The issue is that each page has a different size and it is making the interactions a bit weird. I have a short (in height) page first but the height matches the largest one which makes the content look out of place. If I put the same page AFTER the largest tab, the size is ok. Video in 🧵

Is there a guide for adding material 3 to a material 2 compose project?

I'm trying to set up the startDestination page based on whether the room database has the specified value, but it keeps getting this error

Are material colors defined somewhere in Compose? For example I want to get "Red500". Or do I need to define them myself?

Anyone have an idea why

MaterialTransition

breaks when a

ComposeView

gets integrated into a Fragments XML layout? I have a few fragments using transitions and if I change a piece of the XML layout to use a ComposeView the transitions no longer run.

I've just updated from 1.0.5 to 1.1.0-beta04 and it looks like the elvis operator is no longer working within composables, does anyone know why that is? The second

Text

should be displayed but it isn't - as soon as I replace the elvis operator with an

if

statement then the second text is rendered correctly

Is it possible with the Accompanist Navigation Animation library to perform a Crossfade animation? Currently it fades out the old view and fades in the new one, which is not 100% the same, e.g. you might see the background behind both views while the animation is performed.

How can I measure a composable and update the PaddingValues of another composable without using

Modifier.onSizeChanged

(in other words, without causing an additional recomposition for the entire screen)? Is this even possible? 🤷‍♂️🏽

Hi, We have created a native Kotlin Bridge to communicate with Webview. Calling a Native Kotlin function from a Button click on Webview works well via Javascript Interface like calling a showToast() (Non-Composable) function. However calling a Composable function from Button click on Webview doesn’t work - Like calling AlertComponentDialog() (Composable Function). Any Idea how to call a Composable function from Android Webview?

When using Popup, the content is clipped by system UI even though the activity draws behind it. Am I missing something? Code in 🧵

Hi I’m trying to implement zoomable image. When user interaction(touch down) ends I should run animation which fixes over-zooms and over-scrolls. What code I should run after end of this block?