is there any showcase single activity app doing transitions between different “screens” using compose?

Whats the easiest way to request focus of a TextField in Compose when clicked inside it? My keyboard is showing in front of it everytime and i have to manually scroll up to write in the field

After upgrading compose to alpha12, I'm getting an exception

java.lang.IllegalArgumentException: Anchor refers to a group that was removed

when interacting with a TextField inside of the dialog. Specifically when TextField is focused Stack trace and the sample in the thread 🧵

🚨 1586709: Bump Compose 1.0.0-beta02 | https://android-review.googlesource.com/c/platform/frameworks/support/+/1586709

has anyone been able to use new layout inspector: https://developer.android.com/studio/preview/features?utm_source=android-studio-4-2&utm_medium=studio-assistant-preview#compose-layout-inspector it doesn’t work for my project or in jetnews sample app. It’s just blank

Any idea why Android Studio uses

:app:assemble

to build when running

@Preview @Composable

and how to avoid it? In most cases I need only quick debug build. Regularly building release variant may take pretty long due to R8 and all

Hello, everyone. Has anyone having problems with

./gradlew connectedAndroidTest

using compose-test? My application runs

./gradlew build

just fine, but my instrumented tests does not run. If I play them by Android Studio they work, but not via command line. The issues is

A failure occurred while executing com.android.build.gradle.internal.tasks.DexMergingTaskDelegate

Type androidx.core.animation.AnimatorKt$addListener$1 is defined multiple times

If I exclude the

core-ktx

from the compose-test dependencies, it starts failing other modules in loop. Could anyone help me please?

[Code in thread 👇] I have this code where I'm using the

pointerInput

modifier to allow dragging inside my

Box

. The problem is when the

locked

parameter (and other parameters) change,

onPositionChange

and

onDragStateChange

still executes with the old value of the parameters. Like if

locked

was true by default and the state changes to false, the if statement in

onPositionChange

will still run. I don't know it might be related to some kotlin magic but I was using the now deprecated

dragGestureFilter

modifier before alpha12 and it was working fine with the same code. I've also tried using

detectDragGestures

inside

pointerInput

but no luck.

I am doing this:

return inflater.inflate(R.layout.fragment_hello, container, false).apply {
  findViewById<ComposeView>(R.id.cvHelloWorld).setContent {
    // In Compose world
    MaterialTheme {
      HelloWorld()
    }
  }
}

But then I get: java.lang.IllegalStateException: ViewTreeLifecycleOwner not found from DecorView@d0eeb9[HomeActivity] at androidx.compose.ui.platform.WindowRecomposerKt.createLifecycleAwareViewTreeRecomposer(WindowRecomposer.kt:231) at androidx.compose.ui.platform.WindowRecomposerKt.access$createLifecycleAwareViewTreeRecomposer(WindowRecomposer.kt:1) at androidx.compose.ui.platform.WindowRecomposerFactory$Companion$LifecycleAware$1.createRecomposer(WindowRecomposer.kt:115) at androidx.compose.ui.platform.WindowRecomposerPolicy.createAndInstallWindowRecomposer$ui_release(WindowRecomposer.kt:168) at androidx.compose.ui.platform.WindowRecomposerKt.getWindowRecomposer(WindowRecomposer.kt:216) at androidx.compose.ui.platform.AbstractComposeView.ensureCompositionCreated(ComposeView.kt:184) at androidx.compose.ui.platform.AbstractComposeView.onAttachedToWindow(ComposeView.kt:215) at android.view.View.dispatchAttachedToWindow(View.java:17445) at android.view.ViewGroup.dispatchAttachedToWindow(ViewGroup.java:3326) at android.view.ViewGroup.dispatchAttachedToWindow(ViewGroup.java:3333) at android.view.ViewGroup.dispatchAttachedToWindow(ViewGroup.java:3333) at android.view.ViewGroup.dispatchAttachedToWindow(ViewGroup.java:3333) at android.view.ViewGroup.addViewInner(ViewGroup.java:4977) at android.view.ViewGroup.addView(ViewGroup.java:4768) at androidx.fragment.app.FragmentContainerView.addView(FragmentContainerView.java:280) at android.view.ViewGroup.addView(ViewGroup.java:4708) at androidx.fragment.app.FragmentStateManager.createView(FragmentStateManager.java:536) at androidx.fragment.app.FragmentManager.moveToState(FragmentManager.java:1324) at androidx.fragment.app.FragmentManager.addAddedFragments(FragmentManager.java:2392) at androidx.fragment.app.FragmentManager.executeOpsTogether(FragmentManager.java:2137) at androidx.fragment.app.FragmentManager.removeRedundantOperationsAndExecute(FragmentManager.java:2061) at androidx.fragment.app.FragmentManager.execPendingActions(FragmentManager.java:1957) at androidx.fragment.app.FragmentManager$5.run(FragmentManager.java:496) at android.os.Handler.handleCallback(Handler.java:790) at android.os.Handler.dispatchMessage(Handler.java:99) at android.os.Looper.loop(Looper.java:164) at android.app.ActivityThread.main(ActivityThread.java:6494) at java.lang.reflect.Method.invoke(Native Method) at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:438) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:807) I am using Kotlin 1.4.30, Compose 1.0.0-alpha12

Hi there folks, hope you all are extremely well 👋

Row(
    modifier = Modifier.padding(horizontal = 16.dp),
    horizontalArrangement = Arrangement.spacedBy(16.dp)
) {
    HeighDependsOnContentComposable(modifier = Modifier.weight(1f))
    HeighDependsOnContentComposable(modifier = Modifier.weight(1f))
}

Is there any way I can have both composables with the same height? This is taking the heigh of the tallest one? Is this one of the scenarios where ConstraintLayout would help? Thanks!!! 🙏

Quick question: does Compose require the IR backend? I see this in the docs:

freeCompilerArgs += ["-Xallow-jvm-ir-dependencies"]

but that does not look exactly like the use-IR flag we see elsewhere.

Hi, I implemented a simple NumberPicker widget which works by using

draggable

. Now I want to use it inside a

LazyColumn

, but when I'm picking the number, column's content is scrolling as well. What is the easiest way to block scrolling for parent in this situation? Should I use

nestedScroll

modifier or something else?

Is there a way to style an AnnotatedString with a background that is not just a color (e.g. have a border with rounded corners, as in the JetChat mockup, but not implemented in the JetChat sample)? This would be quite useful for me (in exactly that use case even, in a chat app). An example of what that'd look like would be

monospace

like im Slack web and desktop (although Slack Android also can't handle that correctly)

My project build.gradle file shows a warning:

Kotlin version that is used for building with Gradle (1.4.30) differs from the one bundled into the IDE plugin (1.4.21)

. It's on the line inside buildscript.dependencies: `classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:$kotlin_version"`` . I thought we were supposed to use Kotlin 1.4.30 now? The Kotlin plugin doesn't seem to have an update available. I'm getting a much worse internal compiler error later, so I'm trying to sort out this warning first.

how can we pass Parcelable type using compose navigation?

Can anyone link me to an example of implementing

androidx.compose.runtime.saveable.Saver

? Having a tough time trying to find the source for

androidx.compose.runtime.saveable.samples.CustomSaverSample

Can Ambients be used in a modifier?

Since updating to Alpha12, I have weird errors showing up in my IDE. Several composables like

Text

and

Scaffold

show up with red underline, and the problem says:

'Text( ... ) Unit' is only available since Kotlin 1.4.30 and cannot be used in Kotlin 1.4

First, I have my project set to use Kotlin 1.4.30, so ... what? Also, despite the "error", the project compiles and runs fine ... what gives?

Is there an easier way to do an alpha animation when state changes with compose without using the whole transition api? It’s very heavy, and when I’m animating a lot of things on a screen for different screens it’s very verbose

Anyone come across this when compiling after updating to

alpha12

?

Duplicate class androidx.compose.runtime.savedinstancestate.ExperimentalRestorableStateHolder found in modules jetified-runtime-saveable-1.0.0-alpha12-runtime (androidx.compose.runtime:runtime-saveable:1.0.0-alpha12) and jetified-runtime-saved-instance-state-1.0.0-alpha11-runtime (androidx.compose.runtime:runtime-saved-instance-state:1.0.0-alpha11)

Duplicate class androidx.compose.runtime.savedinstancestate.RestorableStateHolder found in modules jetified-runtime-saveable-1.0.0-alpha12-runtime (androidx.compose.runtime:runtime-saveable:1.0.0-alpha12) and jetified-runtime-saved-instance-state-1.0.0-alpha11-runtime (androidx.compose.runtime:runtime-saved-instance-state:1.0.0-alpha11)

How do you achieve calling a suspending function like snapTo of Animatable inside the draggable modifier callbacks? I tried this and it does not work

val scale = Animatable(0f)
Modifier.draggable(onDrag = {
     LaunchedEffect("test"){
      scale.snapTo(0.5f)  
  }
}

Who wants Compose package name to be changed from

androidx.compose

to just

compose

in light of #compose-desktop, #compose-web, etc and move to beta stage happening soon? ✋ Put another way, if it was originated by Microsoft, or Apple, you can ask yourself if you would want to see it from the

windowsx.compose

or

macosx.compose

package, plus also see it in the imports in all the files where use it, even if for an Android or Linux app.

Hi all! Is it possible to consume the scroll delta offset of a LazyRow? I think I can't just use the ScrollableController modifier.

Can we customize shadow of

Card

as much as we can for

Text

(shadowColor, blur, etc)

Shouldn’t

DrawerState

have a mutable

value

? The way things are working now forces to synchronize internal drawer state with external one (i.e. view model, app state). Wouldn’t it be more idiomatic to export callbacks of user intention to change drawer state so I could update state appropriately myself? Currently it looks like this

fun MyComposable(showDrawer: Boolean, dispatch: (Action) -> Unit) {
    val drawerState = rememberDrawerState(DrawerValue.Closed)
    LaunchedEffect(showDrawer) {
        if (showDrawer) drawerState.open() else drawerState.close()
    }

    // If user swipes or taps on free zone, drawerState.value will change
    LaunchedEffect(drawerState.value) {
        when (drawerState.value) {
            DrawerValue.Closed -> dispatch(CloseDrawer)
            DrawerValue.Open -> dispatch(OpenDrawer)
        }
    }
    ...
}

is ConstraintLayout android related or is a kind of layout that you can implement also in other platforms like web and desktop?

how can I send arguments to ViewModel while using

HiltViewModelFactory

?

'background(Color, Shape = ...): Modifier' is only available since Kotlin 1.4.30 and cannot be used in Kotlin 1.4 I am getting this compiler time error I am using alpha 12 version with canary 6 android studio

Class 'androidx.navigation.compose.NavHostKt' is compiled by an unstable version of the Kotlin compiler and cannot be loaded by this compiler

What does this mean? It happened after updating kotlin to 1.4.30 and compose to 1.0.0-alpha12.