I thought I would make a small project based around Mosaic specifically. To better get to grips with it. I made a small project that others can copy from to get a working project up and running faster. https://github.com/DavidEdwards/MosaicFileBrowser

On 1.0.0-RC1

Dialog

just fill out the whole screen size unlike the previous versions where they just had the proper dialog size by default. I am not sure if its a bug or a feature but I am not sure what is the best way of making the Dialogs have the proper size again? I can add padding around my inside my dialog to make it look better but a static dp padding would not do the same thing since the dialog will still look super large on Tablets.

Has anyone else noticed their @Preview not working in Arctic Fox Beta 5? This is all i see for any preview function i create.

Is there a way to detect user stopping the gestures when using

detectTransformGestures

? Like

onDragEnd

of

detectDragGesture

. I need to reset transformations after user stops the gestures.

This message was deleted.

It seems that

Surface

doesn’t allow click events to come through even if

clickable

is not set. Is it possible to propagate its clicks to parent composable?

Confused about dark mode 🧵

Hi, our project got

compileSDkVersion 29

, after upgrading compose to

rc01

we are facing this issue 🧵

Has anyone used the in-app review API with compose? I'm not sure how to launch the review flow since it needs an activity. Do I need to cast my context to an activity? Or maybe use lambdas to communicate to the activity when I need to launch the flow? https://developer.android.com/guide/playcore/in-app-review/kotlin-java#launch-review-flow

rememberSaveable

is supposed to persist a value across process death. However, I've tried killing the app and restarting it in multiple ways (even cases as simple as 'Live Edit of Literals'!), and every time the state is not persisted. Am I not understanding what

rememberSaveable

is actually supposed to do? A simple example:

var enabled by state { false }
                Button(onClick = { enabled = !enabled }) {
                    Text(text = if (enabled) "enabled" else "disabled")
                }

When the app is started,

enabled

should have the value it had when the app last closed, but that is not the case. It is not 'remembered' or 'saved', it is forgotten and lost.

Are there plans to bring Material's Chip and ChipGroup components to Compose?

Was there any blog post for compose rc01 release?

Has anyone here seen differences in performance between build debug and release build variants. I've seen it where debug builds perform navigation with nav component instantly but release builds (R8 enabled) take a very noticeable second. I don't know if this is Compose or NavComponent related.

Is there any chance to keep the scroll position when swapping the first visible item in an item keyed

LazyColumn

?

Hey..I just started learning compose...how can we set color in spacer.....I want to have a 30 dp space with white color....by default it is coming black color....it tried setting spacer.background(white) but not working....suggest any way to do so...thanx

Can someone invite me to the AV channel？

Is there a compose support for leanback library planned? Did anyone try compose for android TV?

I am currently experiencing an issue where my Column loses its vertical scroll state (even with a rememberScrollState) after a simple A>B, back to A screen navigation. The lists inside that Column do retain their horizontal scroll position though. What's the correct way of troubleshooting this problem? I don't necessarily need an answer but I'd like to know how to approach an issue like this for future reference

Is there some kind

onDestroyView

for composable? For example here listed example when viewModel value assigning as default parameter in composable function by

viewModel()

call. If i understand correct this factory creates (or returns) view model from activity or fragment scope. But what if i develop single activity app with huge number of features on billions screens? Should i use activity view model scope or i must include fragments to my code or there is better way to handle memory in compose?

Software keyboard closes on configuration change I just noticed that when typing in a

BasicTextField

the software keyboard closes whenever there’s a configuration change (rotation, dark mode switch, etc.). I tried fiddling with the

windowSoftInputMode

activity manifest attribute but to no avail. Is this the intended behavior? Is there any way to change it (apart from disallowing any configuration change which is not possible in my case)? PS: The text field also happens to loose focus during the config change.

shrinkResources = true

set my resources as unused when I use it in that way:

@Composable
private fun SomeIcon() = `Icon(painter = painterResource(id = R.drawable.ic_some_awesome_icon), …)`

I don't want to use

keep

for many of randomly shrinked resources and I prefer to keep shrinkResources on. Any suggestions?

Tell me how to correctly place the cursor at the end of the line when focusing

I have a

ScreenA

which is using

MyViewModel

instantiated using

hiltViewModel()

function.

ScreenA

calls

ScreenB

. I want to share

MyViewModel

between both screens. However, I’m popping

ScreenA

when I’m calling

ScreenB

. Is there a way to do this without create a custom

ViewModelStoreOwner

? 🤔 cc: @Ian Lake

Hi, when is the release of Jetpack compose stable version expected?

Is there a way to get the height of a composable? Not the min and max height but the measured height? Code in thread.

I have a

LazyColumn

and I need to do certain actions based if user has scrolled up or down for a certain threshold. What are my best options here? • Use

snapshotFlow

to watch

LazyColumnState

changes, collect delta, act accordingly? • I've also found

pointerInput

+

detectDragGesture

, will it work with

LazyColumn

, should I use it? • Something else?

Hi, I’m using Android Studio Arctic Fox Beta 5. I’m looking at the latest version of the Jetsnack app but none of the previews display properly. When I try to deploy a preview I get an error. The app itself runs fine. Does anyone know what the problem might be with the preview?

Had to flex my trig and circle skills a bit lol

I’m trying to do something a little different and I’m having a very weird “Composition requires an active composition context” 🧵