Any idea how to show a vertical

LinearProgressIndicator

, meaning full height, small width, animating from top to bottom? I tried to simply rotating it by 90°, which surprisingly worked somehow, e.g.:

Modifier
    .height(8.dp)
    .fillMaxWidth()
    .graphicsLayer {
        rotationZ = 90f
        transformOrigin = TransformOrigin(0f, 0f)
    }

But it seems limited to the width of the Composable, hence not filling the whole height. Any other suggestions 😅 ?

Hey, I've just released AdvancedPreview - a library to customise system UI decoration of your Previews :compose:. Link to GitHub More info on Twitter or in 🧵 Here's an example comparison vs standard Preview annotation with enabled "showSystemUi" option.

How can I call a function just once even if there’s configuration changes?

Is there a plan to work on performance of the `runtime`module? My app has huge performance problems and in profiler all the hot paths land in

androidx.compose.runtime

- mostly methods like

ComposerImpl.end

,

ComposerImpl.comsume

,

SlotTable.access

. All other modules like layout, measuring, rendering seem to be OK (except for `Composer.materialize`which is also a very hot path). What do I do - I have simply a Column of like 400 elements, which frankly is not that lot. No LazyColumn because it is even slower and secondly I have to have all the elements instantiated. It is about CfD so I don't have separate release build. (I did manage to get rid of all `sourceInformation-`calls though which did not help much.)

Any idea why my card shadows are clipped off? I seem to not do anything special (code in the thread)

When using the

Text

composable, it seems the text is wrapping to a new line when it does not need to because the the text is so long and has no spaces in between. I noticed if I add spaces to the text it will wrap correctly. First image is wrong (current behavior) second image is what I want. Is this a bug with how Text calculates its

MultiParagraph

object? Or is there a setting I'm missing... Code and images in 🧵

Can I observe state in a state hoisting class? If yes, how can I do it?

I have a traditional 'View' on my route which is supposed to be reused since it takes a long time to load it. I hold it on a shared ViewModel. I only use it on one screen but the screen can be opened from itself (inclusive / keeping only one instance). My issue is that when I open a new instance of the screen from itself, the new screen starts before the old screen runs onDestroy which causes the view to be still attached to the previous screen. I am trying to remove/add the view to/from the parent to fix this but it causes other weird behaviors. Any ideas?

Good evening 👋 Got an interesting question (I think 🤔).. I'm trying to get the resolved width/height of a composable in px, which has a modifier using aspect ratio. Something like:

Image(modifier = Modifier.fillMaxWidth.aspectRatio(1.50f)

And I want to know the resolved height in px, and use that as an offset for another child composable. For simplicity, imagine this

Image

is inside a

Box

and there is another child composable in this box that I want to apply an offset too, by doing some calculation using the

Image

height. (This problem would be easy if the height was hardcoded like 200.dp, but I have to use aspect ratio) I'm guessing the only way to do this is using the

Layout

composable where I would need to measure and layout everything manually... But wondering if there's a more simpler approach that I'm just overlooking. Thanks!

How can I make the “…” works if the text doesn’t have enough space? I tried

overflow = TextOverflow.Ellipsis

with no luck

Hello everyone, I am stuck in a problem in jetpack compose navigation. I do have a case where I have full page screen like login/signup and other settings page and in home page, I need a bottom navigation bar. But time to time I also need to move to full page screen like settings and all from home page. How can I achieve it? does anyone have rough idea, or links to a solution or sample code?

When using navigation compose

rememberSaveable

saves against the nav destination registry. It would be good to be able to call

rememberSaveable

against a SaveableStateRegistry higher up (i.e. a parent graph). Is this possible?

What should I use to only observe state inside composable and trigger recomposition, but without caching the state so I can set the same value? 🧵

Accompanist pager question: This card shows nothing on purpose and is a very small size. maybe like 24.dps in height.

Card(
    modifier = Modifier.padding(horizontal = 16.dp).fillMaxWidth().align(BottomCenter),
    elevation = 8.dp) { //nothing }

When I add a HorizontalPager (replace where it says //nothing with the HP), then the card height becomes the size of the screen. Why and how do you make it only take up the height of the Text?

HorizontalPager(count = 10) { page ->
  // Our page content
  Text(text = "Page: $page", modifier = Modifier.fillMaxWidth())
}

Is it possible to define a z-Index for LazyColumns items? The usecase is a draggable list item that should be drawn on top of all other list items so it wont disappear behind list items below it while it is being dragged

I’m seeing a weird layout issue with the TopBar of one of my views and I’m stumped as to how to fix it at this point. Code and screenshots in 🧵

Hello, if I upgrade to Kotlin

1.6.0

and Compose to

1.1.0-beta04

my Webview (inside AndroidView) in LazyColumn doesn’t scroll anymore. I tried to change to Column with verticalScroll but same issue. I can’t find any change related to this. Any help?

So i have a wrapper function that styles a card. The issue i’m having is that if i pass a testTag through the modifier, and that modifier is passed along to the Card function i’m calling, i end up with two nodes with the same test tag:

@Composable
fun MyCard(modifier: Modifier = Modifier, ...) {
    Card(modifier = modifier, ...) { ... }
}

Regarding kotlin version 1.6.0. I've been out of the loop for a bit, but now I updated my project to latest compose 1.1.0-beta04 and it requires kotlin 1.6.0. Weren't there a bunch of things that were broken because of kotlin 1.6.0? Should I just hold off on compose beta04? it doesn't even look like AS has a 1.6.0 kotlin plugin?

Hi everyone. I have a question regarding TextField. According Material Design specification the height of TextField should be 48.dp, in compose default height of TextField is 56.dp. Is this on purpose or there is some mistake?

Is there an easy way to export the images for all the previews? I'm thinking of sharing them with my UX team so they can inspect them.

How do you apply a new theme to something like an Image? Most of our icons use SVGs, and in the View world we use attrs & themes to change the theme of our icons from greyscale to destructive or disabled. One SVG -> multiple themes to change the different stroke colors

is it expected to use Material3 with Material2? There are a few components that are in the Material2 library that aren’t in the Material3 library so I wasn’t sure what the status of that was

Hi I’m trying to integrate facebook ads network via Admob mediation to my app But I’ve encountered an error while restoring view state when using

AndroidView(factory: ..)

inside Compose LazyList As a workaround I checked duplicate ids and reset them to random id Error message: IllegalArgumentException: Wrong state class, expecting View State but received class… This usually happens when two views of different type have the same id in the same hierarchy.

One thing I don't get with CompositionLocals is that I need to "get" my local outside of my composable. i.e. Why do I have to do this?

val backHandler = LocalOnBackPressedDispatcherOwner.current
MyButton(
    clickEvent = { backHandler?.onBackPressedDispatcher?.onBackPressed() },

instead of this

MyButton(
    clickEvent = { LocalOnBackPressedDispatcherOwner.current?.onBackPressedDispatcher?.onBackPressed() },

Hey, I’m using Lottie with Compose - and the animation repeats indefinitely. For instrumented tests, this means the test gets stuck waiting for composition to complete. I’ve tried setting the

composeTestRule.mainClock

autoAdvance

to false, and then manually advancing the clock - but this doesn’t work very well when I actually want the UI test to take control of the clock. Lottie has the ability to pass in a property representing whether an animation should run a finite number of times, or infinitely. I could pass in a different value for this to the Composable - but this feels akin to making something mutable just for the purpose of testing..

Has anyone had any reports of missing/ignored keystrokes when typing fast in compose? I received a bug report with video-proof this morning and I swear I saw a post about it on here earlier - but I cant find it now!

Is Compose 1.1.0-beta04 compatible with Kotlin 1.6.10-RC ?

Hello everyone, I want to achieve a screen background similar to this one. does anyone have idea how can I achieve this. The middle separator must be an arc cutout.