I'd like to create a progress button, where the text is replaced with a circular progress when it is in a loading state, but I don't seem to be able make it work. I would like the button to keep its size when the loading progress is showing, does it mean I would have to do my own measurements? code and current state in 🧵

It seems that setting activity's

android:configChanges="uiMode"

on beta08, theme will not work properly when changing the device's dark theme, which is working on beta07.

I get message

Unable to resolve activity for: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] cmp=ru.rt.designsystem.android.compose.test/androidx.activity.ComponentActivity }

since updated to beta07 when calling

@get:Rule
    val composeTestRule: AndroidComposeTestRule<ActivityScenarioRule<ComponentActivity>, ComponentActivity> =
        createAndroidComposeRule()

when updating to beta08 nothing changes. Anybody knows how can it be resolved?

Shouldn't this be a breaking change? This break the behavior for drag event handling which we only consume the change if needed before but after beta08 will always consume the change even if we don't need to.

Hi I am seeing something weird with the bottomSheetScaffold where the following scenario is leading to the bottom sheet not showing up. Starting with a collapsed state -> call expand on the bottomSheetState -> Do some work -> call collapse on the bottomSheetState -> call expand on the bottom sheet state again and the sheet doesn't expand. Upon debugging I do see that the bottomSheetState.isCollapsed is set to true before I call expand a second time. Also putting a debug pointer in the animateTo function the

latestNonEmptyAnchorsFlow

never collects. Am I doing something wrong here ? Fixed 😄

anyone else experiencing that code completion window disappears constantly because the compose views are being updated?

Space doesn’t allow background

What is the minimal set to use

Preview

in compose? A have

build.gradle.kts

like i’ll post in thread shortly, but i receive error when try to build preview

Anyone having any sample or any knowledge about how to architect multi screen app (say 30-35) in pure jetpack Compose with MVVM? Do you guys use single activity and single viewmodel and handle it there only? Or you prefer creating multiple activities or fragments?. The question is related to how to properly architect the MVVM based Compose app.

Hello fellow developers, Is there anyway to set animation completion time for AnimatedVisibilty? I checked docs https://developer.android.com/jetpack/compose/animation#animatedvisibility but nothing is mentioned regarding the time. By default animation is too fast for my requirement.

I upgraded kotlin 1.5.10, upgrade compose compiler to 1.0.0-beta08 and upgrade navigation-compose to 2.3.5. Got issue at navigation library, Could not find androidx.navigation:navigation-compose:2.3.5. Although, navigation compose work in alpha version (2.4.0-alpha02). Anyone have face similar issue in 2.3.5 version.

This message was deleted.

Default AS compose project gives this error:

Process: com.recoverrelax.samplecompose, PID: 25973

java.lang.NoSuchMethodError: No static method drawRect-w2WG-Gw$default(Landroidx/compose/ui/graphics/drawscope/DrawScope;JJJFLandroidx/compose/ui/graphics/drawscope/DrawStyle;Landroidx/compose/ui/graphics/ColorFilter;Landroidx/compose/ui/graphics/BlendMode;ILjava/lang/Object;)V in class Landroidx/compose/ui/graphics/drawscope/DrawScope$DefaultImpls; or its super classes (declaration of 'androidx.compose.ui.graphics.drawscope.DrawScope$DefaultImpls' appears in /data/app/~~N4u3ZpQc0VQmQWkVneo2fA==/com.recoverrelax.samplecompose-7T8CqVR-pfvTlb_4zi7DpQ==/base.apk)

at androidx.compose.foundation.Background.drawRect(Background.kt:111)

at androidx.compose.foundation.Background.draw(Background.kt:103)

at androidx.compose.ui.node.ModifiedDrawNode.performDraw(ModifiedDrawNode.kt:102)

at androidx.compose.ui.node.LayoutNodeWrapper$invoke$1.invoke(LayoutNodeWrapper.kt:260)

at androidx.compose.ui.node.LayoutNodeWrapper$invoke$1.invoke(LayoutNodeWrapper.kt:259)

at androidx.compose.runtime.snapshots.SnapshotStateObserver.observeReads(SnapshotStateObserver.kt:121)

at androidx.compose.ui.node.OwnerSnapshotObserver.observeReads$ui_release(OwnerSnapshotObserver.kt:75)

at androidx.compose.ui.node.LayoutNodeWrapper.invoke(LayoutNodeWrapper.kt:259)

at androidx.compose.ui.node.LayoutNodeWrapper.invoke(LayoutNodeWrapper.kt:53)

at androidx.compose.ui.platform.RenderNodeApi29.record(RenderNodeApi29.android.kt:156)

at androidx.compose.ui.platform.RenderNodeLayer.updateDisplayList(RenderNodeLayer.android.kt:229)

at androidx.compose.ui.platform.RenderNodeLayer.drawLayer(RenderNodeLayer.android.kt:210)

How can I force to recompose LazyColumn when the list does not update even if the list is changed?

Generic question: How can I pass a lambda for a screen using Navigation? 🤔 Specific explanation: I’m creating a Generic Error screen which should have an option to “Retry”. So my plan was

if (error) navController.navigate(ERROR_SCREEN)

, but I’m stuck in how to pass this action to the ErrorScreen… Any thoughts?

is there any standard way of preserving the same viewModel instance across composables navigation, for instance, BottomNavigation?

[SOLVED] I updated Compose in my sample (example-dogs) to 1.0.0-beta08, now if I tap 4 dogs at the same time (thus "opening 4 pages quickly"), the app crashes with the following exception (see in thread) this crash is new and was not present in 1.0.0-beta07

exception in thread:

how to make the icon to match parent size

Is there any API introduced in Beta 08 for Screen Transitions Animations ?

I’m trying to add an error message below the

TextField

. I’m setting

isError

to true ~and adding

semantic { error("Message") }

modifier~… do I need to do something else?

does DrawScope.drawRoundRect support only partial round corners (ie, only at start-top and start-bottom) ?

When using a text field is there a way to prevent the composable from triggering the onValueChange callback? For example let's say I only want the text field to allow numerical input.

I have a Compose view that scrolls with maybe 56 ‘subviews’ and performance is not good. I know the Compose team is still working on optimization, but is there anything I can do to measure performance or provide info to the team to assist? I tried using the latest layout inspector, but it just crashes the app. Thanks.

This message was deleted.

Hey guys, what's the correct way to listen for scroll position on Lazy column?

I’ve got Sony TV which runs Google TV (which is still Android TV afaik), so is it possible to run Compose on it? :) or may be #compose-desktop fits better? Did anyone try it already?

I'm interested in writing Arrow Optics integration with Compose's state management, but I'm not how or even if it's possible to create new mutable state types. Creating naïve implementations of

State<T>

and

MutableState<T>

that read and write eagerly seems to work for now (haven't tested snapshotting extensively yet), but I'm concerned that I might need to be observing some types like

dependentStateOf

does. Is there a way to integrate my new state types nicely with the existing state types?

Hi after updating to beta08, whenever I scroll a lazy list my app crashes, with the following crash exception: