Is there any way to get the position of the Cursor within a

TextField

? I know about the

selection

of the

TextFieldValue

. But I need the coordinates. As an alternative: Is there any way to scroll to the current Cursor positon within a scrollable

TextField

or one within a scrollable container?

Are variable fonts in TTF format supported by Compose?

Is there an

animateContentSize

modifier that does not clip the item to its bounds? And I’d love to understand the reason that it is a default without a parameter that can change it @Doris Liu My use case is that I have a simple Card inside a RecyclerView that I’d like to animate when it changes, but the fact that it’s forced to clip bounds cuts the shadow and makes it look super ugly. Is there maybe a different API I should be using instead? For now I simply copy-pasted the private functions existing in the library and removed the

clipToBounds

call and it does exactly what I wanted it to.

Today I noticed the existence of a modifier against a “default custom Modifier” (see example below). Does anyone know what is the reasoning? And what is the alternative to provide a custom behaviour that can be replaced? That feels like the most intuitive and obvious way of doing it. For example (that is not a real code as

bringIntoView

is actually mandatory but you should get the point):

@Composable
private fun MyTextField(
    // other attributes
    modifier: Modifier = Modifier.bringIntoView(), // optional modifier that can be overriden.
) {

And the warning:

Optional Modifier parameter should have a default value of Modifier

Implemented Fibonnaci animation using Compose. Inspired from

@physics_only_

Instagram reel but was removed now. Tried with different approaches but finally went with Recursive Composables (it was fun) GitHub repo Original animation in 🧵

Edit: Solved. We’re running into:

java.lang.NoSuchMethodError: No virtual method setContent(Lkotlin/jvm/functions/Function0;)V in class Landroidx/compose/ui/platform/ComposeView; or its super classes (declaration of 'androidx.compose.ui.platform.ComposeView' appears in /data/app/~~80WnH7kFvYH_QJwuutqQpw==/com.ourapp.android.debug-V0ZNfKBI9LNUKhjnWxUOKg==/base.apk)

We have a

buildSrc

and so tried to follow the guidance here

<https://issuetracker.google.com/issues/176079157>

however when I add

implementation("org.jetbrains.kotlin:kotlin-gradle-plugin:1.5.31")

to my buildSrc gradle file, I get a

Plugin request for plugin already on the classpath must not include a version

Has anyone else run into this?

Is Compose compatible with Google's Live Translate? It seems like it has an effect directly on the view system, which Compose doesn't use (but I've got no way of testing it)

Can I make a TextField or some other component that is invisible but sill receives keyboard events?

Looks like version 1.1.0-beta04 with Kotlin 1.6.0 was released today. Should we expected a stable version 1.0.x with Kotlin 1.6.0?

Should Compose honor the "Remove animations" accessibility preference in Android 12?

I finally solved my Compose testing problems, after spending quite some time trying to track down some very obscure bugs! With Compose, when testing screens, you call 

composeTestRule.setContent { MyScreen() }

  - if you’ve written Compose UI tests, you’d be familiar with this. If you need to run the tests against a particular activity, for some reason, you can use 

androidComposeTestRule<MyActivity>

In my case, 

MyActivity

 calls 

setContent { MyScreen() }

 during 

onCreate()

. So, what ends up happening, is the test instantiates 

MyActivity

, which calls 

setContent()

, and the screen is composed, with its ViewModel and various dependencies. While this is happening, the test calls its own 

setContent()

 and the screen is composed again, in parallel! This causes all kinds of nightmarish problems. tl;dr Make sure when testing Compose, that you only call 

setContent()

 once per test. And be careful about which 

Activity

 you use to host the test, if you need one!

Compose TextField's cursor is overlaying system ui (keyboard, statusbar, etc) -- Is this a known issue? Is there a workaround? I couldn't find anything.

Hi All, what is the point of keeping theme.xm files and reference them in the manifest file since theming colors are defined on the

MaterialTheme

color fies

I need to launch a coroutine in the

onDispose

of the DisposableEffect but I'm getting a

JobCancellationException

. This is probably due to the coroutine scope that I'm using (its the one that

rememberCoroutineScope

returns) that's not available anymore when I'm executing the

onDispose

block. Wondering how I can solve this?

At 1:31 the speaker says something along the lines of ~"composables are completely different from views. it doesn't use the view hierarchy at all" https://www.droidcon.com/2021/11/10/testing-jetpack-compose-ui/ Maybe a bit pedantic, but that's not entirely true right? Composables on android still essentially just live in a view hierarchy?

Hi folks, in the 1.1.0-beta03 version of compose material library we have added a new ExposedDropdownMenuBox component that is fantastic, but the default design is the filled dropdown menu style, not the outlined one which is what i'm looking for. is there a way to configure it such?

We’re happy to announce the availability of Compose Multiplatform 1.0 - first stable release of JetBrains UI toolkit for Kotlin. See and blog post at https://blog.jetbrains.com/kotlin/2021/12/compose-multiplatform-1-0-is-going-live/ for details of what is being released. Enjoy Compose Multiplatform!!!

Hello devs. I want to have shared element transition in a hybrid app where we have fragments and the fragment content is composable. I’ve created the following composable to have an

AndroidView

that wraps a

ComposeView

and the content of the

ComposeView

could be any composable

@Composable
fun SharedElement(
    modifier: Modifier = Modifier,
    transitionTag: String,
    @IdRes viewId: Int,
    content: @Composable () -> Unit
) {
    AndroidView(
        modifier = modifier,
        factory = { context ->
            ComposeView(context).apply {
                transitionName = transitionTag
                id = viewId
                setContent {
                    content()
                }
            }
        }
    )
}

The problem is when the first fragment gets destroyed, the content of shared element gets decomposed as well and we can’t have a smooth transition between fragments. Ideally, shared composables should decompose when the element transition ends but I couldn’t find a way to do that. Any idea how this shared element transition can be nailed with composables and fragments?

Should I report bugs in the following situation: I released an app, and I see Crashlytics crash reports with a stack trace in Compose, but no frames from my code. I can't reproduce the crash. My guess is there are some bugs in Compose causing it, but is a stack trace and message not enough for a report? Example in thread.

Is there some way to disable overScroll effect in HorizontalPager by Accompanist?

Do I have to specify all Material3 colors? I would imagine

primaryContainer

would be generated from

primary

for example

Hey all, How do I get rid of that grey bottom line on the text field?

How do people handle full screen `@Preview`s? I have seen opinions previews should only be used for individual composables, not screens, but I also think the XML layout previews were useful and I would like a preview of an entire screen.

Is there a way for a component up in hierarchy to be notified when none of its not immediate nested children has focus? I.e. if I have deeply nested set of TextFields and want to do something when focus is lost? I tried adding onFocusEvent to this grand-parent component, but it receives

hasFocus = false

immediately after one of the children receives

hasFocus = true

Hi 😄 I added AnimatedVisibility to each item in a lazyColumn. I want to invoke an action at the end of tween animation. I can add listener to 

animateColorAsState

 ; however,  this causes to take action while tween animation is running. Is there any way to understand  when the exit animation completed?

I was checking the

MotionLayout

for Compose and cannot understand whether it supports specifying

OnSwipe

gestures that we can define inside scene files in XML. Is it something that will be added later on, because the docs say that the first version of

MotionLayout

for Compose supports only a subset of features?

what is the Compose’s advantage over Flutter?

I have an AndroidView where i get some custom Font via

ResourcesCompat.getFont()

Is there any possibility to render this view in the preview? It failes with an exception "Font resource ID #0x7f080000 could not be retrieved" If I build and deploy the application it all works fine

does someone have the code for a CircularProgressInIndicator with rounded edges on the progress bar?