Guys, I’m haunted with

Class 'androidx.compose.ui.geometry.Offset' is compiled by a new Kotlin compiler backend and cannot be loaded by the old compiler

. Please halp. I did everything including adding

useIR = true

,

freeCompilerArgs += ["-Xallow-jvm-ir-dependencies", "-Xskip-prerelease-check"]

in all places,

compose true

and all. How can I validate that IR is actually enabled? Using Kotlin 1.4.10, Compose 1.0.0-alpha03

Just went through all the

LayoutModifier

implementations just

PainterModifier

i didnt understand what its good for ?

In the “Composable functions can run in parallel” section (https://developer.android.com/jetpack/compose/mental-model#parallel), I just noticed something

Because of this, writes like this are not supported in Compose; by prohibiting those writes, we allow the framework to change threads to execute composable lambdas.

I was wondering what “prohibiting those writes” means? Like I understand why we shouldn’t do it but how is the system enforcing it right now? I don’t see anything that’s stopping me from doing that.

Hi, I'm trying to animate the UI by changing ConstraintSet in ConstraintLayout. But it reflects the UI changes immediately without animating. Am I missing something or is it something not implemented yet? Thanks in advance. You can find the code in the thread.

Why does compose feel so stuck ？

Hello everyone, the below code is recomposing ui for every item in the list on scroll. This is being done even when there is no change is any of the items of list and number of items in list is 100 is there any way to avoid this

ScrollableColumn() {
                LazyColumnFor(items = list) {item ->
                    getSampleDataRow(data = item)
                }
            }

Hi! I'm having some difficulties to understand how my components are being recomposed. I'm making a simple dice roller app and I want to animate every dice every time I produce a new roll. The thing is that if a dice gets the same result as the previous roll it won't animate again. This is working as expected I suppose. But there are sometimes when a new result won't animate the dice again and this I don't understand. I'd like to fix that and force the animation even if the result is the same

Hi. What is the best way to make an opaque color overlay over an image (safety gradient) in Compose? Creating a surface just for it seems like an overkill and it seems there is nothing like foreground modifier.

Same issue on Emulator with API 24 as well. I am really curious if this is a problem with AndroidView with MapView or AndroidView completely.

I do really like compose, but if it gets delivered with the preview as broken as it is now, it’s going to end up DOA.

Hello! I’ve been playing with

transitions

and

transitionDefinitions

for a sample app I'm working on. I noticed that I was having the same issues over an over while handling multiple transitions. Basically,

transition(toState = , initState = )

is a bit confusing at first try. It's great for a single animation that triggers immediately (i.e. the Rally app circular animation). However, it's easy for the state to get out of sync / to cause undesired transitions. I thought it may only be me, but I've seen the same problem in a post someone did. If you deep dive in the implementation, you'll notice: • Actual transitions work great. Really powerful API. • Problems: a) first transition is triggered right away. b) weird validations to display content because animating state and actual state are out of sync. With that I'm not trying to bash the author, of course, actually I had almost the exact same issues. Here I'm just pointing out a few ways in which I think the current API can be misused. There are solutions for those problems, yes, but I don't think they are that easy to figure out right now. So after dealing with some animations, I spotted a pattern with my implementations. Basically I had: • a class with the state. Same as in Jetsurvey app, which I used as example. • within that state, hold a

current

and

animatingTo

states. They work as the source of truth for the transition. That looked like the ideal solution for some of my transitions (not all of course, some work just fine without extra classes holding the state). Given that a lot of the logic was reused, I created a base implementation instead. Now, my question is: is this the correct approach? I really don't want to reinvent the wheel, or complicate things with unnecessary logic.

👋 Both PaintStyle and DrawStyle expose

Fill

OR

Stroke

styles. In DrawScope’s

drawPath

method, documentation says :

Whether this shape is
     * filled or stroked (or both) is controlled by [DrawStyle]

What is the appropriate way to do the “both” scenario ? We could draw the path twice with two different DrawStyles but is there a cleaner solution to do that ?

I got a problem with the State Codelab. In Chapter 6 you are building an input field which gets cleared when you press "add". but as soon you start typing again the text reappears. this seems buggy and I don't know why this is happening. I tested the finished solution from google but it also happens there. Did you also got this problem? why is this happening? Link: https://developer.android.com/codelabs/jetpack-compose-state?return=https%3A%2F%2Fdeveloper.android.com%2Fcourses%2Fpathways%2Fcompose%23codelab-https%3A%2F%2Fdeveloper.android.com%2Fcodelabs%2Fjetpack-compose-state#5

I can't figure out how to convert files from the MediaStore to one of the objects that the composable Image() expects. Is there a way to convert from a Descriptor, Bitmap, Drawable (w/o res id?) to ImageAsset or Painter?

I am sharing also here, my experience about using Kotlin/React for creating Kotlin compose functions that look exactly like Jetpack Compose. Does anyone here have any info to share about future plans of extending JetpackCompose to the Web? It looks like a very natural road: https://kotlinlang.slack.com/archives/C3PQML5NU/p1600781686119000

Hi guys, another basic question, as I am still a beginner. I am trying to create custom radio buttons. I've looked at the code for RadioButtons but I can't see how to make sure that a button is deselected when another one is clicked. Here is my code:

@Composable
fun BoxCards(color: Color, gradientColor: Color, text: String, size: Dp) {
    val (selected, onSelected) = remember { mutableStateOf(false) }
    val tlRadius = animate(if (selected) 48.dp else 20.dp)
    val radius = animate(if (selected) 0.dp else 20.dp)
    val boxModifier = Modifier
        .size(size)
        .weight(1f)
        .clip(
            shape = RoundedCornerShape(
                topLeft = tlRadius, topRight = radius,
                bottomLeft = radius, bottomRight = tlRadius
            )
        )
        .toggleable(value = selected, onValueChange = onSelected)
        .background(
            VerticalGradient(
                0.0f to color,
                0.5f to gradientColor,
                1.0f to color,
                startY = 0.0f,
                endY = with(DensityAmbient.current) { 150.dp.toPx() }
            )
        )
    Box(
        boxModifier,
        gravity = Center
    ) {
        Text(text = text, color = Color.White)
    }
}

I've used a tutorial by one of the Google team for the animation... Is there a simple way of converting my BoxCards into radio button behaviour?

Hey, how about having the ripple indication the default for .clickable? Seems a lot rarer that people wouldn't want it. Thoughts?

Hooray! 🎉 1434551: Scroll performance optimization for LazyColumnFor/LazyRowFor | https://android-review.googlesource.com/c/platform/frameworks/support/+/1434551

Hello, I would like to know what is the recommended practice when we want to import and use an icon with Jetpack Compose? We should use a drawable or convert it in Kotlin? If it is the second one, there is any plan to migrate automatically a vector in Kotlin? Thanks in advance!

Hi, can someone give me a recommendation of a good video course / tutorial of jetpack compose which contains all the new features and best practices until now?

No luck for me and compose codelabs 😞. I am currently doing the state codelab. Yesterday I posted about a problem where a TextField somehow remembers it's state. Problem only occured on one Samsung though. Now I am in the next chapter "7 Dynamic UI based on state". At the end an onClick action is extracted into a lambda variable and set when you press the "add" button or send an IME action via keyboard. The IME action doesnt work for me. In my code an empty Todo item is added, in the finished solution the "Done" button on the keyboard only closes the keyboard. This time the problem occurs on the Samsung and a current emulator. I would be interested if the IME functionality is working for anybody else and if I should invest time in troubleshooting ;)

Has anyone tried adding Jetpack Compose to existing KMM project. As soon I add the required dependencies for compose in the project gradle file, it just does not work. I am on Android Studio 4.2 C 12. Tried to copy the settings from perfectly working Compose examples, still no luck

How can I draw a dividers between

Column

children?

what is the difference between

modifier.clip(RoundedCornerShape(20.dp).background(Color.White)

and

modifier.background(color = Color.White, shape = RoundedCornerShape(20.dp))

Trying to Toast inside of a composable event. How are you supposed to get a context?

TextField(
            value = textState.value,
            onValueChange = { textState.value = it },
            imeAction = ImeAction.Done,
            onImeActionPerformed = { imeAction: ImeAction, softwareKeyboardController: SoftwareKeyboardController? ->
                Toast.makeText(ContextAmbient.current, "asdf", Toast.LENGTH_SHORT).show()
            }
        )

is

consumeScrollDelta

lambda in

ScrollableController

receives the delta in

dp

now? or i am doing something wrong 😄

Is there a reason why

DirectionalAlignment

is a private class? Being able to create an alignment with custom vertical and horizontal bias could be really useful. In my case I need to move a component around, and this seemed like the easiest way:

@Composable
fun Sample {

    val offset = animatedFloat(initVal = ...)
    onActive { offset.animateTo(...) }

    Stack {
        SomethingThatMoves(Modifier.align(DirectionalAlignment(offset.value,offset.value)))
    }
}

Given that it's private, I just copy & pasted the class, and worked perfectly. Is there another easy way to accomplish that?

Hey, any specific reason of why I can’t see the source code of any compose related class?