Please tell me what's wrong

I have an interesting design to implement. Have a LazyColumn which can consist of any number of items but as whole this list should be shown on a card. So it should have rounded corners at the top and bottom and also a border along the whole thing. I visualized it on a screenshot - the red lines delimit LazyColumn items. I will probably need to draw these backgrounds directly on a Canvas, but maybe you can think of a more high-level way of doing that? I can't think of any - the border always outlines the whole shape, can't restrict it to just a part of a shape.

Not seeing a subtitle property in TopAppBar. Is this coming soon, or possible to implement in another way?

Is this change intended to solve internal issues, or external ones? Exhaustive when breaking when enums are changed is a feature of kotlin, I would think if consumers are writing exhaustive whens on these things then they’d want them to break if the API changes.

Hey everybody, I just encountered some bizarre behavior and I don't think it's intentional. So when using a

LazyVerticalGrid

, you can pass an instance of

LazyListState

as a parameter, which itself takes

initialFirstVisibleItemIndex

as a parameter:

LazyVerticalGrid(
    cells = GridCells.Fixed(cellsPerRow),
    state = rememberLazyListState(initialFirstVisibleItemIndex)
)

The problem is that the index passed to

rememberLazyListState

is used as a row index instead of an item index. So if I pass 5 as

cellsPerRow

in the above example, and I pass 7 as the

initialFirstVisibleItemIndex

, I would expect the second row to be the top of my list, but instead it's 7th row that is at the top. At this point I usually have to do this to get the correct behavior:

rememberLazyListState(initialFirstVisibleItemIndex / cellsPerRow)

Is it possible to get scroll offset in pixels for

LazyColumn

? Can only see

firstVisibleItemScrollOffset

which is relative to items in the list

I’m having a weird problem with

Icon

. All my

Icon

turned black when using in a composable and I have to use

tint

to turn it into the right color. Does anyone else having the same issue?

Really simple question, but what's the easiest way to have two equally sized buttons in a row. Code in thread

As a rule of thumb, you should create a view model to hold your state […] when the composable is close to the root of the screen.

When that’s not the case, for examples, composables that are reusables […], don’t use a view model , instead create a regular state holder class to manage state and expose events.

This is said shortly after 7:32 in the video, the slide at that time refers to a

Carousel

and a

ExpandableCard

but I couldn’t find any related code in the compose-sample project. Does anyone hasve a concrete/sharable example of such a “regular state holder class”?

Hi folks! I need run

infiniteTransition

with scale effect for 3 different views, but each transition should start with delay after previous.

dalay

in AnimationSpec doesn’t help. Cuz I need only start delay not for every cycle

I am trying to use the top current item of

LazyColumn

as a state and recompose another composable based on it. I have found

listState.layoutInfo.visibleItemsInfo

which works mostly except that it gets updated with every minuscule scroll and causes performance issues. Is there a pattern to implement filter or debounce like behavior with compose state? Is my approach completely wrong?

I want to implement mechanism to force select app day-night theme. For example: if set returns it, else returns

isSystemInDarkTheme()

. For example this fun will be called

isAppInDarkTheme()

. I also want to recompose all dependent composables. Which parts and mechanism of compose is better to use to achieve behavior like it?

btw, does the locale parameter of the @Preview works for you ?

@Preview(locale = "fr")

it remains in english for me 😄 (I'm providing a values-fr/strings.xml) and of course I also tried

@Preview(locale = "fr-rFR")

Hi folks! Is this the right way to show SplashScreen or there is a better way?

@Composable
fun SplashScreen(navController: NavController) {
    SplashScreenContent()
    val coroutineScope = rememberCoroutineScope()
    SideEffect {
        coroutineScope.launch {
            delay(2000)
            navController.popBackStack()
            navController.navigate(Screen.Home.route)
        }
    }
}

implementation("com.google.accompanist:accompanist-glide:0.10.0")

🙁 What an accompanist wants? https://google.github.io/accompanist/glide/

Hello, i'm trying to only change a variable only when this column is focused, but it keeps getting the inicial last_location value when it is not focused. PS: location is a state variable

Hi! One question. how can I make all the content scroll when the bottom

LazyColumn

scrolls? Should I set all the content inside a

LazyColumn

?

keeping with last post... Is a good or bad practice to do this?

fun LazyListScope.postsListEmpty() {
    item {
        Box(
            modifier = Modifier.fillMaxSize(),
            contentAlignment = Alignment.Center,
        ) {
            Text(text = "No items")
        }
    }
}

What would be the best practice for defining multiple required arguments for compose navigation? Let’s say there’s multiple ids I need to pass. How about something like this?

screenA/itemId/userId/someToken

Or is below better even though the syntax is for optional arguments…

screenA/itemId?userId={userId}&someToken={someToken}

Is TextAlign supposed to be working in

BasicTextField

? The three fields below all have text set

"x"

, and alignment is TextAlign.Start, Center and End. I'm setting the alignment from text style.

Is there some example of sticky header in compose?

Is there a way to align text to the right and have other text leftalign based on that first text's contents? (Pictures in thread)

Hello All! I have a question about state hoisting. Based on the docs and recent videos aiming for stateless composables should be the way to go. State is recevied as a function param and we transmitted through lambas. I find this quite compelling but am currently working on a rotationary dial. Within I have so inner state ( texture angle, gesture angle, pointer info etc). Does it makes sense to push for a stateless component on this scenario? It feels weird that my domain layer needs to be aware of such thing

People who are building design systems in Compose: Are yall using prefixes/suffixes on your component functions to identify them as part of your design system? E.g.

Button

->

MaterialButton

. (Would love to hear your thinking about this in the thread! Why are you or aren’t you using prefixes?)

Is it possible to initiate outside of a composable function? I use my navController on

onNewIntent()

of my activity but it can sometimes throw a null exception due to it not being initiated yet.

I've seen some comments about how Previews work way better in Bumblebee but I had to see it with my own eyes. There's a huge difference. Congratz to Compose Tooling team for such a great update 😛arty-parrot:

Is there such thing as an auto size text view in compose? I searched cs.android.com without being able to find anything related to compose. Like this?

Is it possible to group composable to apply modifier on this group? For example i have scrollable column with 50 elements, but i want to apply padding only for composables from 17 to 33. Is it possible? Note that if i wrap it to another layout then all will be collapsed no matter which layout i would to select

Should

rememberSaveableStateHolder()

restore the scroll state of a

LazyColumn

in a child composable?