Bringing some more attention into, I've tried almost everything and couldn't find a solution https://kotlinlang.slack.com/archives/CJLTWPH7S/p1646232232500439

Hi all, when using

lazyListState

how could we change set the scroll animation rate when scrolling to top

More compose tinkering done in the past half hour 🍳🍳

Facing https://issuetracker.google.com/issues/192478844 and seems there was no action on it. Everything is internal and it's impossible to modify ModalBottomSheetLayout. Anyone have an idea for how to handle edge to edge design and ModalSheets?

Hi, Is there any way I can assert Row's horizontalArrangement/verticalAlignment/modifier props in test?

Hi. Does this error means anything to someone? We can't find the problem. We have some UI tests on a hybrid app with both an

ActivityTestRule

and a

ComposeTestRule

. We recently migrated some TextViews to Compose and now a lot of tests fail with:

androidx.test.espresso.IdlingResourceTimeoutException: Wait for [Compose-Espresso link] to become idle timed out

tried deleting `build`+`.gradle` folders, Invalidate Caches… etc but nothing is working

Filed a bug on

firebase-android-sdk

https://github.com/firebase/firebase-android-sdk/issues/3517

I am using Webview in Scaffold, everything is fine, but when I try to scroll the Webview, it opens the drawer menu, it doesn't happen when I am using LazyColumn. Any way to handle it?

Hello, what could cause

buildFeatures.compose = true

to be ignored? Compiling Compose code fails as if I didn't enable it, and colors don't show in the gutter for

Color(0xWHATEVER)

calls.

My only solution has been to restart the program, which is very annoying, since it seems to happen around every 15 refreshes or so

Pretty sure I found a bug in

RangeSlider

if you constrain its width it doesn’t render the second range button, because it goes outside of that space. Also if you don’t set

Modifier.fillMaxWidth(0.85f)

it will push anything after it out of view which I’m pretty sure is not the intended behaviour. I’m using Compose 1.1.1. Also if you constrain the max width the progress indication get’s really wacky.

Is this log printed by compose?

Does anyone have a similar issues?

Is there a test rule that waits for a manual fonction call before launching the Activity? I have something like:

@get:Rule
val activityRule = createAndroidComposeRule<SplashScreenActivity>()

But I have some individual setup for each test to do before the activity is launched. So I would like to, in my

@Test

function, do some initialization, launch the test, and then perform clicks, assertions, etc.

I’m using a

VisualTransformation

. In the textfield, when it sees

{{user-id=1234}}

it’ll convert it to “@username”. What’s the best way to calculate the offset using

originalToTransformed

and

transformedToOriginal

?

Just FYI: The play store had an article recently that included a modifier for recomposition highlighting. https://github.com/android/snippets/blob/master/compose/recomposehighlighter/src/m[…]le/android/compose/recomposehighlighter/RecomposeHighlighter.kt

My solution to this problem ended up being having each nav graph destination provide their own

Scaffold

if needed. That eliminated the problem of having to awkwardly animate the bottom/top nav and produces the smooth animation one would expect. I’m not sure if this is or isn’t a good practice, but it seems to get the job done.

Wondering if there are any updates on any sort of “official” support for converting vector drawables/svg to Compose `ImageVector`s?

For anyone using Insets from Accompanist, v0.24.4-alpha now deprecates it in favour of the official WindowInsets support in Compose. If you find something that is difficult to migrate then please let me know. We have migration docs at https://google.github.io/accompanist/insets/

I have a

LazyRow

implementation where I prevent simultanous clicks on single items via a

LaunchedEffect

(key is a boolean mutable state, if the state gets false, i.e. some item is clicked and clicking is now disabled, I delay for 100ms and then set the state back to enabled). How would I test such a thing with

ComposeTestRule

? My initial idea was to use

ComposeTestRule

s

mainClock

and call

adanceTimeBy(101)

, but that doesn’t seem to work at all (not even with double the time). Any pointers?

Does Compose have an issue with Shader warm up at all?

Can anyone help me on this one? https://stackoverflow.com/questions/71502444/compose-two-composables-overlaped-and-constraint-with-them It's about using ConstraintLayout that the link is not working as expected, I think it's a thing of naming and I'm missing something

Is there a way to make sure that an animation doesn't execute until the view is visible on screen? I have a

animateDpAsState

, but it seems to be running right when the

targetValue

changes even though the view itself is not yet visible I am using both Android classic views + compose inter-operably, basically what Im doing is, I turn off this

ComposeView

until a condition is met, when this condition is met, I then turn the

ComposeView

visibility to true but it seems like the animation already happened before the view was visible on screen? Not sure whats happening but my log in

finishedListener

is not executing

Is there a way to disable D-pad scrolling in a

Pager

/`LazyList`? I have a

LazyRow

in the contents of a

Pager

and it scrolls the pager while navigation through the

LazyRow

using D-pad/arrow keys.

Can anybody get link to an article about paging in compose without Paging Library?

Hey I’m back here, did some more digging into the issue.. and seems like the issue happens because of using a ConstraintLayout with weights to create the fragments for the master/detail screen. Somehow internally I’m receiving updates on the size of the detail screen and is making the composables to get infinite recompisitions on the width of the screen and so not being idle. Replacing the ConstraintLayout in the xml for a LinearLayout with weights as well the message is more clear:

2022-03-17 17:03:24.046 12464-12464/com.compose.playground E/MonitoringInstr: Exception encountered by: Thread[main,5,main]. Dumping thread state to outputs and pining for the fjords.
    java.lang.IllegalStateException: Vertically scrollable component was measured with an infinity maximum height constraints, which is disallowed. One of the common reasons is nesting layouts like LazyColumn and Column(Modifier.verticalScroll()). If you want to add a header before the list of items please add a header as a separate item() before the main items() inside the LazyColumn scope. There are could be other reasons for this to happen: your ComposeView was added into a LinearLayout with some weight, you applied Modifier.wrapContentSize(unbounded = true) or wrote a custom layout. Please try to remove the source of infinite constraints in the hierarchy above the scrolling container.

for now I made a workaround to avoid the recomposition fixing the size.. but its not ideal.. any pointers on how to fix this? should I file an issue somewhere?? thanks again! some logs of the recomposition updates:

Am I recomposing??
Box boxMaxWidth = 1280.0.dp, maxWidth = 1280.0.dp
Box maxWidth2 = 1280.0.dp
 Am I recomposing??
Box boxMaxWidth = 833.5.dp, maxWidth = 833.5.dp
Box maxWidth2 = 833.5.dp
 Am I recomposing??
Box boxMaxWidth = 833.5.dp, maxWidth = 1280.0.dp
Box maxWidth2 = 833.5.dp
 Am I recomposing??
Box boxMaxWidth = 833.5.dp, maxWidth = 833.5.dp
Box maxWidth2 = 833.5.dp
 Am I recomposing??
Box boxMaxWidth = 833.5.dp, maxWidth = 833.5.dp
Box maxWidth2 = 833.5.dp
 Am I recomposing??
Box boxMaxWidth = 833.5.dp, maxWidth = 1280.0.dp
Box maxWidth2 = 833.5.dp
 Am I recomposing??
Box boxMaxWidth = 833.5.dp, maxWidth = 833.5.dp
Box maxWidth2 = 833.5.dp
 Am I recomposing??
Box boxMaxWidth = 833.5.dp, maxWidth = 1280.0.dp
Box maxWidth2 = 833.5.dp
 Am I recomposing??
Box boxMaxWidth = 833.5.dp, maxWidth = 833.5.dp
Box maxWidth2 = 833.5.dp
 Am I recomposing??
Box boxMaxWidth = 833.5.dp, maxWidth = 1280.0.dp
Box maxWidth2 = 833.5.dp
 Am I recomposing??
Box boxMaxWidth = 833.5.dp, maxWidth = 833.5.dp
Box maxWidth2 = 833.5.dp

and the branch where is reproduced: https://github.com/danimontoya/compose-playground/tree/simplified

Hello I'm using ConstraintLayout and I can make a box grow with a child Box without cutting the text of the children when the text of the first is too small. Is there any way to set the

width = Dimension.fillToConstraint

and then say that the first box has the min width as the second Box? The only constraint is that the first box can group and it makes the second one bigger, but the min width of the first one should be the same width as the second box. I add a reproducible code down below.

ConstraintLayout() {
    val (title, description) = createRefs()
    Box(
        modifier = Modifier
            .padding(start = 4.dp)
            .background(color = Red)
            .padding(horizontal = 16.dp)
            .constrainAs(title) {
                top.linkTo(<http://parent.top|parent.top>)
                start.linkTo(parent.start)
                end.linkTo(parent.end)
                width = Dimension.fillToConstraints
            },
        contentAlignment = Alignment.Center
    ) {
        Text(text = "Dynamic value", maxLines = 1)
    }

    Box(
        modifier = Modifier
            .padding(end = 4.dp)
            .background(Color.Magenta)
            .padding(
                bottom = 5.dp, start = 8.dp, end = 16.dp, top = 4.dp
            )
            .constrainAs(description) {
                top.linkTo(<http://title.top|title.top>, margin = 16.dp)
                start.linkTo(parent.start)
                end.linkTo(parent.end)
                bottom.linkTo(parent.bottom)
            },
        contentAlignment = Alignment.Center
    ) {
        Text(text = "Fixed Value")
    }
}

I have a small form using a

DropdownMenu

and then a

TextField

. How can I make it to automatically focus the

TextField

and show keyboard after something was selected in the

DropdownMenu

? I tried to set a

FocusRequester

to the `TextField`'s

Modifier

and call

focusRequester.requestFocus()

from

DropdownMenuItem.onClick()

but it only focus the

TextField

and does not show the keyboard automatically.

Is there a way to disable scrolling via arrow keys in

LazyRow

?