Hi 👋 , I hope one of you can be of help to me. I have a LazyColumn that gets populated with different sections that contains a LazyRow. Inside that LazyRow I would like to track when a user has been viewing a given element for more than 2 seconds. This works fine By getting the firstVisibleItemIndex

val state = rememberLazyListState()
val visibleIndex: Int by remember {
    derivedStateOf {
        state.firstVisibleItemIndex
    }
}

LazyRow that takes the state

LazyRow(
    state = state
)..... bla bla

And then a LaunchedEffect on the visibleIndex

LaunchedEffect(visibleIndex) {
    delay(2000)
    onMetricViewed(metrics[visibleIndex], visibleIndex)
}

My problem now is that this also runs on the second element in the LazyColumn which is far from visible (maybe around 5%). I've tried with calculating the visibility of items but couldn't come up with something that worked as I wanted it to. How can I make sure that

onMetricViewed(metrics[visibleIndex], visibleIndex)

is only called if I can actually see the full height of the element in the LazyRow? 🤔

I need to create a Dialog with wrapcontentheight in the modifier but seems that Dialog doesn't accept a modifier. Any help about how to solve this? Thank you

why is not using the material scaffold padding parameter such a big deal? warranting a need for and Error in the code and I have to suppress it ?

@SuppressLint("UnusedMaterialScaffoldPaddingParameter")

I seem to remember there were a few weird things with inline

@Composable

functions, but I can't find where it's documented. Does anyone know?

Does anyone knows why i’m getting this white screen? — Using Scaffold at top level

Slider accessibility I cannot find a way to define what TalkBack reads when the Slider value is changed. In my example my slider can have 3 values 0, 1, 2 which then mapped to Walking Speed values: Slow, Medium and Fast respectively. TalkBack reading the percent values of the thumb is not very helpful in this case. Is it possible to override the value read on Slider value change without ruining the functionality of the Slider? (being able to change the value by swiping up or down and by double tap-and-hold then sliding left and right is the basic way a Slider can be used with TalkBack, I do not want to loose this)

What’s the easiest way to provide a spring() spec to an animation, but with an initial delay before it starts? For a tween there’s a

delayMillis

which makes this convenient. From what I understand this isn’t the case for the spring one since you want to maintain momentum from potential earlier animations or something like that, is this the case? Now I’m thinking of doing something like

val animatableProgress = remember { Animatable(0f) }
LaunchedEffect(Unit) {
    delay(300)
    animatableProgress.animateTo(1f, spring())
}
// use animatableProgress

to use this exact thing, but I feel like I may be missing some API which makes this simpler for me.

Can you trust the layout inspector recomposition count on a debug build, or should you always be running in release mode?

So i’m trying to replicate the maxHeightInLinesModifier from compose 1.4 so that it can work with existing versions. I’m having some trouble with the embedded calculations. For whatever reason, it things the paragraph with a single line is 59px tall, and that the paragraph with 2 lines is 111px tall. I would have expected the 2 line paragraph to be at least twice as tall (118px) plus some additional for the line height on the text style. Not sure what I might be missing here.

@Composable
@Preview
fun TestParagraph() {
    val density = LocalDensity.current
    val fontFamilyResolver = LocalFontFamilyResolver.current
    val placeholderText = "H".repeat(10)

    val paragraph1 = Paragraph(
        text = placeholderText,
        style = MaterialTheme.typography.body1,
        spanStyles = listOf(),
        maxLines = 1,
        ellipsis = false,
        density = density,
        fontFamilyResolver = fontFamilyResolver,
        constraints = Constraints()
    )

    val paragraph2 = Paragraph(
        text = (1.. 2).map { placeholderText }.joinToString("\n"),
        style = MaterialTheme.typography.body1,
        spanStyles = listOf(),
        maxLines = 2,
        ellipsis = false,
        density = density,
        fontFamilyResolver = fontFamilyResolver,
        constraints = Constraints()
    )

    val height1 = paragraph1.height
    val height2 = paragraph2.height

    Column {
        Text(text = "${height1}")
        Text(text = "${height2}")
    }
}

is there a way to observe if an IME animation (either hiding or showing) is currently in progress? we have some code which has a slight delay after calling keyboard

hide()

before doing the next thing.. the UX feels nicer than without the delay, but the delay itself feels flimsy — in fact we probably need a condition that says we don’t have a delay on older API levels which don’t animate the IME at all. it’d be cool if there was some kind of

isImeAnimating

state I could watch for this purpose, or something I could use to create a derived state to produce my own

isImeAnimating

, but I can’t think of anything immediately and a quick search hasn’t turned anything up

I’m really curious about this, what do you folks think? 🙏

Premature optimizer question:

@Composable
private fun VerticalSpacer(size: Dp) {
    Spacer(modifier = Modifier.height(size))
}

Does creating helpers like this add some overhead?

Maybe a shot in the dark, but maybe Ian (or someone from Firebase perf team lurking around). Any chance that we get perf stuff for compose destinations like we get for activities and fragments?

hello everyone I have a crash reported in firebase, but I don’t have much more than the stacktrace I send it in case someone else has happened to it

How would I go about creating a composable that has a collapsed form, showing minimal content and a fully expanded form which shows everything. I'm trying to copy how the miniplayer/player is in YouTube. I want it so the components move and resize as its going to a different state. Is that possible in compose?

Hi, I have interesting issue 😄 code is

Scaffold() {paddingValues ->
        Column(
            modifier = Modifier
                .fillMaxSize()
                .padding(bottom  = paddingValues.calculateBottomPadding())

and screen in bottom on old navigation looks like …

I have to say that I set <item name=“android:navigationBarColor”>@android:color/transparent</item>

Does anyone know how to fix it? 🙏🏻

I’m using compose navigation in the app I wanted to know, how do I navigate to a destination which is not in my graph? ex: I have a feature F1 whose navigation graph is G1, from within one of the destinations of G1 I want to navigate to another graph G2 which is not part of G1 app/F1 G1 app/F2 G2

Hi Can someone please help me in achieving this UI(first image) in compose? Till now I have been able to achieve this (second image) with

Popup

and

PopupPositionProvider

The background and arrow are the most challenging part as it’s position will be dynamic, for eg. arrow will be on top normally and it might be on bottom if the anchoring view (trailing icon of text view) is on bottom of screen and very less space is available below. And the arrow should point exactly to the “help” icon as shown in first image

It seems like if I pass a data class that has internal visibility to a Composable, then even though the Compose compiler metrics output identifies the parameter as stable it seems to still cause recompositions when the value doesn't change. Removing the internal or adding @Immutable fixes it. Is this expected? Took a few hours to debug that one...

I’m developing a custom layout component (a

Table

) and now I want to draw lines between rows and columns using measures I’ve calculated inside Layout code. How do I do it? Do I have to add artificial components for each line, lay them out and then draw? Or can I somehow feed data after measurements to something like

drawBehind

?

Is the material3 website wrong about what's supported in Android? For instance, I was looking for

FullScreenDialog

, as listed here https://m3.material.io/components/dialogs/overview - but it's definitely not listed here https://developer.android.com/reference/kotlin/androidx/compose/material3/package-summary !

Hi, Hope everyone is doing great! I’ve been using Jetpack Compose for a few months now but I can’t seem to find a proper Arch pattern and not in the perspective of the ViewModel but I also want the good approach to handle the State holder and CRUD operations on them. Let me know all the resources Thanks in advance!

[Compose Navigation]How to avoid repeat request when screen got retained ？

Hello, does something exist like

ItemTouchHelper

in compose for Lazy* ?

Hey folks! Trying to test a

ModalBottomSheetLayout

but I am not sure if the assertions are working right. All I am trying to do is to call a button click which opens up the sheet and asserting the sheetState to see if it is visible. Every assertion is failing for some reason. Code and logs in the thread ⬇️

Hello... can anyone help with this question on SwipeToDismiss? https://stackoverflow.com/questions/74825269/android-jetpack-compose-androidx-compose-material-swipetodismiss-suspend-fun-dis

I wonder if there is any reason that

Stroke

is not a data class? I miss

copy

method…