Hi How can I do list like below in compose? Should I use

LazyVerticalGrid

?

Android Studio - Bumblebee | 2021.1.1 Canary 5 Released with an important bug fix for switching and redeploying to devices 👍 https://androidstudio.googleblog.com/2021/07/android-studio-bumblebee-canary-5.html

❔ Hey folks. At some point semantics text merging changed and started disallowing this (

findByText_merged_fails

). Before this change, the test here would match the

Box

successfully and pass. What’s the new correct way to match that Box?

Can anyone please tell me how to share a ViewModel in compose inside navigation? I am getting two instances of the ViewModel from two different compose functions, whereas I need to share just one instance of it. Please answer this question in StackOverflow if you can, which no one was able to answer so far. Thanks! https://stackoverflow.com/questions/68548488/sharing-viewmodel-within-jetpack-compose-navigation

Hi. Is a BottomSheet meant to be drawn behind a BottomBar? It doesn't look right.

Roadmap: https://developer.android.com/jetpack/androidx/compose-roadmap

Hi all! You have already picked up on this, but ... the day has come, Compose is officially 1.0! Thanks so much for all the feedback you gave us in the last two years, it has helped make Compose a better product, it's your product too! We hope you like the changes that we published to our documentation, tutorial, and the roadmap. Now, happy composing! https://goo.gle/compose-is-stable

BTW: there is also a new version of Android Studio 😅

I would like to capture the UI emitted by Jetpack compose as a Bitmap. In XML this was done like this: Basically takes a view as an input parameter and returns it as a Bitmap.

//take screenshot of the view added as an input argument
fun takeScreenShot(view: View) : Bitmap {
    val bitmap = Bitmap.createBitmap(
        view.width,
        view.height,
        Bitmap.Config.ARGB_8888
    )
    val canvas = Canvas(bitmap)
    view.draw(canvas)
    return bitmap
}

What is the equivalent of this in Jetpack compose?

I was trying to achieve EdgeToEdgeLazyColumn example but it is not occupying till statusbar, everything is same except I am using

AppcompatActivity

instead of

ComponentActivity

and

Theme.MaterialComponents.DayNight.DarkActionBar

instead of

Theme.Material.Light.NoActionBar

. Also there is reason behind using I'm using theme and Activity because I am also using ReviewManager which takes AppcompatActivity reference. Any help on this will appreciated, desired output pic is attached

Do sample links resolve correctly in documentation now? It has been a major pain since the very beginning (yeah I know about cs.android.com but searching there everytime is quite tedious)

Jetpack Compose has been released as 1.0, but I am still missing animatedVectorResource that has been in beta09 and then removed. Does someone know how to go around that? It is still in the official docs... https://android-review.googlesource.com/c/platform/frameworks/support/+/1753821

One thing I found in the stable version to be careful of is the fact that compose treats two lists with the same values as equal, even if the references aren't the same. I was having my viewModel modify the original list, then set the listState.value equal to ArrayList(oldList). This did not trigger a recompose. Code showing this with a basic array in thread.

Had anyone been able to get the

paddp

compose live template to work? https://developer.android.com/jetpack/compose/tooling#live-templates It never does anything for me. While

comp

works as a live template. I want to file a bug, but I think I'm just invoking it incorrectly?

androidx.navigation:navigation-compose:2.4.0-alpha05

seems to have bug/weird behavior after upgrading from

2.4.0-alpha04

. I don't know what exactly is causing this, but It can be triggered when using with bottom nav bar like shown here. Problem: When re-selecting the same tab (i.e clicking already selected tab), the screen becomes empty. It doesn't happen when current destination is the root graph's startDestination. I first noticed this on my app, then confirmed it by trying it on tivi and upgrading nav compose to

2.4.0-alpha05

. Screencast: https://photos.app.goo.gl/RPur9JpEZwS8srt28

If may I ask, do ripples ripple in 1.0? 😀 Havent tried it yet

Hi everyone, I heard that Jetpack compose was released 1.0 version. It's really great, but someone can tell me how can I create recyclerview with flexboxLayoutManager by jetpack compose. Thanks you all, have a nice day

How to save state that has other saveable state?

class ChildState {
    // ....
    companion object {
        val Saver: Saver<ChildState,*> = // Has been defined
    }
}

class ParentState(val childState: ChildState) {
    // ...
    companion object {
        val Saver: Saver<ParentState,*> = // How to save the childState using ChildState.Saver?
    }
}

If you use a TopAppBar, do you think there should: a) be a separate instance of the top app bar associated with each screen, so that the screen owns the logic for populating the bar and handling actions that are relevant to that screen? Or b) should the top app bar sit at the root level, and be shared between screens

Hi! I'm trying to get rid of

appCompat

and `material`dependencies, usinig just a

ComponentActivity

from

androidx.activity:Activity:1.3.0

, but i receive a crash:

Process: com.alorma.composedrawer, PID: 13088
    java.lang.AbstractMethodError: abstract method "void androidx.lifecycle.DefaultLifecycleObserver.onCreate(androidx.lifecycle.LifecycleOwner)

When using

ComponentActivity

with no theme applied manifest.. and without any app compat or material.. it adds a toolbar... how can it be removed?

Sorry for bothering so much... I'm inspired today 😅 I'm trying to use

accompanist

system ui controller lib, following this: https://google.github.io/accompanist/systemuicontroller/ But i found that on light theme icons are not show :S

Anyone have any opinions on passing a function through a deep hierarchy using CompositionLocals? Is it okay to do that?

How can I reset certain states when some other states change? I don't know if that's the best way to state my problem, so let me elaborate. I have a composable function that displays an image (well a box with an image inside), that supports double tap, pinch-zoom, panning and glide. All of the states like current scale level and offset are internal to the composable. It takes a ImageBitmap as its input. Now, in the main activity, there's the option to display different images. Now whenever I display a different image, I want to reset current zoom level and pan. Of course, when the ImageBitmap passed to my composable, only the displayed image is changed and any previous zoom and pan are retained. How do I reset these internal zoom and pan states, whenever ImageBitmap is changed, without exposing the internal states to the main activity?

I have a bottom nav that is drawing under the navigation bar. To fix this, I thought all I had to do was add navBarPadding

BottomNavigation(
    modifier = Modifier.navigationBarsPadding(),

which "works" so that my bottom bar isn't behind the system nav, but now I'm seeing elevation like my bottombars height wasn't actually changed. Still working on a minimal repro (happening in my actual project currently), but has anyone encountered this before? Before and after attached

Does Compose 1.0 still use Kotlin 1.5.10?

Is there any advantage of declaring magic numbers as constant variables outside composable functions?

I’m still having issues with LazyColumn and Exoplayer with Compose 1.0. The scrolling is very slow. I’ve tried to use only one exoplayer instance vs one for each item but he didn’t change the experience. I’ve 3 questions: • Is it a known issue with compose and exoplayer ? • Is there any best practices for this use case? • Should I revert using recylerview ?

I have navigation destination route like

routeX?argA={argA}&ArgB={ArgB}

. When I query the BackStackEntry from NavController, I would like to use navController.getBackStackEntry("`routeX` ") without optional param as optional params can grow in future. But current api fails as it expects optional param as well. Any reason why the route should match optional params on query?