Question about what options exist when using components from material3 (DatePicker) while not really having a m3 color scheme compatible color system in your app in🧵

Is there a way to override the Preview name when using

PreviewParameterProvider

?

Hi guys 👋 , I hope one of you can shed some light on my issue.. I have a composable (dialog) that takes a list of items that should fill out a column which has a modifier that wraps the content height. The list of items comes from an api response so the composable should update once they are ready. The issue is that if I start by setting an emptyList and then update it later (viewModel observe)… then I don’t see the items as the wrap content height for some reason doesn’t update. If I fill out the list from the start with fake data that corresponds to the same amount of items from the api then the composable shows all items. Also if I set the height to not wrap but fillMaxHeight then the items will also be visible.. If I use a LazyColumn then I can see all items but I need to scroll as the height still doesn’t change.. In short… Items get updated correctly, the composable takes the new list of items and inflates the views with the new items and data.. But the height doesn’t change.. But I need it to adapt to the new number of items and wrap that height.. Code in thread…

Hi guys, I am drawing progress bar in canvas. I did that with the help of amazing tutorials/examples in canvas. There is a problem in some part i.e. I want to add a transparent part after the Gradient color line end. I don't understand why this tiny vertical line comes and I didn't figure out properly.

What's the reasoning for the difference between default values for composable lambda parameters like in

OutlinedTextField

where they are nullable, and

Scaffold

where they are empty lambdas?

Will there be any BottomSheet composable from Material which allows applying custom scrim colors & draggable to full screen even with content which occupies only half the height of the bottomsheet.

Hi , Is there a way to make ModalBottomSheetLayout non dismissable.

How can I scroll to position in DropDownMenu?

Hi is there way, we can improve the

weight

modifier in better way in

Column

.

A question about the

LazyListScope.items

method which adds a count of (lazily loaded) items (as used by the Paging library): Is it correct to assume that the stability requirement for

key

applies to real items only and placeholder item keys may be unstable? Details in 🧵.

Are compose fling velocity tied to some Android OS settings like animation speed that can block compose animation API? Or where there any changes recently about those? Got a user report with a video showing that there's no fling effect at all on his device, all list just scroll by what he move no velocity after.

Is anybody running UI tests for Compose with Robolectric? I don't have much experience with the tool, but spinning the Android env is a pain in the butt. I've seen some articles online but I was wondering if that would be reliable and whether I will hit a wall two weeks in 😅

Hi, why is recomposition not working in this Compose UI test code?

@get:Rule
val composeTestRule = createComposeRule()

@Test
fun test_recomposition() {
    var recomposed = false
    composeTestRule.setContent {
        Box {
            println("composed!")
            if (!recomposed) {
                recomposed = true
                currentRecomposeScope.invalidate() // <--- try recomposition here
            }
        }
    }
}

Anyone working on a game engine with Compose?

If I want my entire page to scroll on overflow content, is

Modifier.scrollable()

my best option?

Hi, how can I animate a row in lazycolumn when the content changes? The row gets recomposed as the items in lazy list are keyed and the key changes

Hi, In xml we use

View.INVISIBLE

to just don't show the view at all, but it still takes up space for layout purposes. What is the alternative in jetpack compose?

AnimatedVisibility(
    // true or false
) {
    Button() // button code.
}

I've a dialog and I would like it to fill the max size without "stretching" the parent, basically to make the blue box fill the full width. I tried using

fillMaxWidth()

but then it stretches the parent even if it's not needed. Is there a way do to this?

I’m Looking at refactoring our navigation compose NavGraph to include nested navigation. What is the recommendation for having a destination that is used in multiple nested graphs? Should those be different navigation routes or is it OK to use the same route within multiple NavGraphs?

Found this interesting. Might be of some use to you all: https://github.com/PatilShreyas/compose-report-to-html

Hi all, I am software engineer at Google specializing in Compose Layouts. We just recently landing an experimental API for Flow layouts and many of you have already started working with it. Currently we only support main axis arrangement in the form of horizontalArrangement in Flow Row and verticalArrangement in FlowColumn. We are looking to also support cross axis arrangement and would like to get feedback on the community on preferred naming conventions. Here is a document I wrote up. Feel free to comment on this thread or the document with your thoughts. Thank you! https://docs.google.com/document/d/e/2PACX-1vTywxWWgJFoqjVLudq8el1hHZcOt5Yx6GooD1vSYFFVqyxMw99r-YwUfpzjO9iAFIVveLbDkDx50_HX/pub

Is there any way to mark

CharSequence

as being stable? I'm using it as a way to pass around either

String

or

AnnotatedString

.

If I have a composable function in a class, and the class is not inferred to be stable, and I reference something from that class in the composable function, compiler metrics shows that function as restartable but not skippable. Should I be marking that class as

@Immutable

?

public class ComposeTest {
  private val foo: CharSequence = ""

  @Composable
  public fun Render() {
    println(foo)
  }
}

restartable fun Render(
  unstable <this>: ComposeTest
)

I have a

LazyColumn

with an

AndroidView

which wraps a

WebView

LazyColumn {
    AndroidView(
      factory = {
           WebView()
      }
    )

   //other stuff
}

The WebView has horizontal scrolling but while scrolling it, the lazy column & android view “fight” over the scroll input. If your horizontal scroll has any kind of vertical component to it, the lazy column will start scrolling. Other native views in the same lazy column that scroll horizontally work correctly (as in if your scroll is partially vertical, the lazy column won’t scroll errantly) Has anyone run into this before?

I am currently working with https://github.com/adrielcafe/bonsai and have my tree successfully synchronised with my model in both directions. There is one problem remaining though. If I have a large tree and expand and select a node programmatically (i.e. not by clicking on it) so that it may not be currently visible, how can I then scroll to the position of the node so that it becomes visible? Am I missing some API here or am I just blind?

Is it advisable to use TextField when having to edit large chunks of text? (Large as in several hundreds of KB). Are there any better existing widgets for this?

Is there an

Arrangement

that gives each item the same amount of “room” and then aligns within that room. Like if I put each item in a box of the same weight and aligned within the box?

Does anyone know how to disable the window inset animation for

Modifier.imePadding()

?

Hey everyone I'm using JetBrains Compose version

1.4.0-alpha01-dev938

with Kotlin Version

1.8.0

where I have a common module named

composeMain

that contains common composables for both Desktop and Android. I've just realised that

rememberSaveable

is not persisting values through screen rotations on Android. I tried downgrading to the latest stable version

1.3.0

as well but I'm still facing the same issue. Is this a known bug? Or I might be doing something wrong here?

Hello, Can someone please explain the problem of using key in lazy column? I’m facing the same problem.

<https://stackoverflow.com/questions/74381205/removing-item-from-the-list-causes-wrong-display-in-lazycolumn>