When using a ModalBottomSheetLayout, is there a way to track when the user dismisses the modal bottom sheet by clicking on the screen above it and not on the predefined button to close the bottomsheet itself?

Hi! I have a

DropdownMenu

with some

DropdownMenuItem

I want to show some items with icon and some without... but i got this: code in 🧵

just upgraded to Arctic fox 3.1 RC 1 and the preview works perfect with 1.0.0-rc02 :cheers:

Hi, I have a data class, is it correct to mark this class as

@Immutable

and what will be the difference with

@Stable

Code in 🧵

I'm trying to implement 2 different contents for

ModalBottomSheetLayout

and I'm having a weird effect, please see video. Sheet layout seems to visually collapse on start. Any ideas? Source code in thread.

There are

Dp

,

DpOffset

and even

DpRect

, but no

DpSize

… For some reason, I need

DpSize

much more often than offset or rect. Could you please add it for completeness?

does marking

sealed class

with

@Immutable

has any effect on subclasses?

Trying to create a server-driven theme system, and would like to measure where recompositions occur when some theme components are changed. What’s the best way to detect recompositions? Something like using

SideEffect

etc, and putting logs in it, or something?

What’s the proper way to create layout like this: • Row with many items • Each item is measured according to its content • Row height is max height of all items • All items are laid out to fill this height, so their content can be properly aligned to bottom or center ?

I have a question about state management for snackbars. Currently we followed previous suggestion here about having a

showSnackbar

state and clearing it in on result, If user navigates to another screen before the snackbar result, the composable is not able to update its result because of cancellation. Then the user goes back to the Composable with a new composition and shows the snackbar again. Is there a better way of handling snackbarstates? Code in thread

Will the stable release of jetpack compose come with koltin 1.5.20?

Hey everyone! With Jetpack Compose, we’re able to erase almost all use of LiveData (previously we used it to facilitate observing respecting the lifecycles). Yet we still use LiveData when using savedStateHandle in the ViewModel. Why is it that there isn’t a way to do this using Flow? For example, if we have a form with fields, we’ll usually write the logic for each field in the ViewModel like this (using savedStateHandle to keep the state in case of process death):

val nameFieldLiveData = savedStateHandle.getLiveData(NAME_FIELD_KEY, "")
val nameFieldFlow: Flow<String> = maxPassengersLive.asFlow()

fun setNameField(name: String) {
   nameFieldLiveData.value = name
}

It would be great if there was a savedStateHandle.getFlow which returned a MutableStateFlow, right? Our main issue with LiveData is the fact that it holds a String! instead of a String. So in the case of my example, nameFieldFlow becomes a Flow<String!>, unless I specify the type explicitly. And I always forget to specify the type explicitly

I have question on how to take screenshots of a composable function programatically : 1. In My App, I let users choose an Image from their gallery, then write some text on top of the image in an EditText field 2. Allow them to drag the EditText field across the canvas which is the image that was just chosen 3. Then take a screenshot of the view as a Bitmap and upload the Bitmap to a cloud storage for other users to view I am having trouble with step 3, Is there currently a way to take screenshots ? Taking Screenshots were quite straightforward in xml layouts

Hello, I have a question about alerdialog, this component only can have a title and a text? according the API one alertdialog have these parameters

title: (@Composable () -> Unit)? = null,
text: @Composable (() -> Unit)? = null,

 both are composable but the name indicate something specific (text). I have tried to create a OutlinedTextField in text parameter with a strange result, it would not be better to create a content parameter?

Hi, I'm getting this error when deploying preview Composable to device

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

is it a known issue ? using compose 1.0.0-rc02

Is there a reason

androidx.compose.ui:ui-util:1.0.0-rc02

includes a

fastMap()

but not a

fastMapIndexed()

function? Would it be the same as if using kotlin std lib's

mapIndexed()

?

Im assuming no, but is there currently a way to animate the

BottomAppBarCutoutOffset

of the BottomAppBar?

I have a

Text

that is made both

.draggable

and able to detect

onTap

(with

.pointerInput

detectTapGestures

) if a flag is true (and neither of those if the flag is false). The

.draggable

Modifier has an

enabled

parameter which I use for this purpose, but

.pointerInput

does not, so I add and remove it from the Modifier chain as appropriate. I tried adding

.draggable

in the same manner, for consistency, instead of using

enabled

, and it seems to work just as well. I was wondering though if there was any reason to prefer

enabled

over changing the Modifer.

Was there any consensus reached on "using dp instead of sp" for text? For example if I'm a bad guy and want to ignore font scaling settings, can I do that without repeating conversion each time?

Just updated Android Studio to Bumblebee Canary 4, created a new project and got this error after launching the app

java.lang.AbstractMethodError: abstract method "void androidx.lifecycle.DefaultLifecycleObserver.onCreate(androidx.lifecycle.LifecycleOwner)"

I'm using compose 1.0.0-rc02 and activity 1.3.0-rc02. Does anyone know what's wrong? 🧵

Have a question about the navigation component. If I instantiate a class that is not a viewModel in the NavHost within one of the compose route elements, will this object be disposed of when navigating to another route? All the examples I see are specific to viewModel objects here.

Hey, I’ve spend the last couple of hours figuring out when

@Immutable

and

@Stable

should really be used to make the most out of them. I couldn’t really find any use cases for them, as even marking a class with

@Immutable

annotation doesn’t mean it will always be skipped from recomposition after being altered (code in the thread). Does anyone have any code examples showing benefits of using either one?

Does anyone know if the release version of compose is going to support kotlin 1.5.20? It seems odd that it’s a full release, yet the rc01 of compose chokes if you try to use it:

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

what’s even odder is that i’m using rc02 of compose and it’s compiler.

Hey, I am using Compose Build262, and the

uiTooling

dependency requires

androidx.activity:activity-compose:1.4.0-alpha01

, which is not (yet) published to https://maven.google.com/web/index.html#androidx.activity:activity-compose

Hello, I have multiple LazyRows inside a LazyColumn. I would like to be able to scroll one of the LazyRows and that the others will scroll as well. How can I achieve it? I have tried using rememberLazyListState() but with not luck (Only the last LazyRow scrolled, the others stayed)

I made a terrible hack to get

RenderEffect

in Compose! https://gist.github.com/tadfisher/dc908504a7189be82c8df2151ede590b

This might be a dumb question but.... is there any way to download the official jetpack compose documentation? I'm boarding a red eye flight and was going to work on my app while flying but with no internet it might be a little annoying being new to compose.

1. Is a variable cached by

remeber

function only initialized during

Initial Composition

or is it always initialized during

recomposition

but with the last saved value? 2. Is 

val state: Int = remember { 1 }

 as good as 

val state: Int = 1

 because in both cases 

state

 variable is immutable and once it is initialized it can only be read? 3. In

val state: MutableState<Int> = remember { mutableStateOf(1) }

, can you do something like

state.value = 2

to change value of state and which would trigger recomposition.

In compose, how can we update single item in paging list (paging 3 library)? I wants to update paging list (

like

property of an object) when user click on like button.