How would you go about building this composable? To me, It's two distinct piece (the blue background card) and then the "bottomCard" composable. The tricky thing about the bottom card composable (that I keep iterating on) is that the icons (soccer balls) are supposed to be aligned with their respective score, but they also have to be offset so that they are 40% on the card, but 60% is hanging off the top to create this cool affect.

where can I found the compose compiled files ?

I don’t seem to get

@Immutable

to work correctly for me - why do my list items recompose, when changing only a

isLoading

flag of my UI-State? 👉 Code in 🧵

is the code for the toolbox (which is based on Compose now) available anywhere?

what are these collapsable elements in the Toolbox? Toolbars?

What is the right way to deep link into a destination in which its graph’s start destination has arguments. Should I pass those arguments to my deep link? Please see example in thread. I’m having an issue where I’m not able to navigate to the destination because of the missing parameters for the start destination.

Custom Layout Question (some sample code in the 🧵)… I’m writing a basic Grid composable that takes a number of columns and a content composable. To do the measuring of the child measurables, setting the width contraints is pretty straight forward. But I’m curious about the height constraints for each measurable. It seems like I should take into account the heights of previously measured items (well, rows), and calculate the max available remaining height (based on the overall maxHeight constraints passed into the layout) and then pass height constraints into the measure function for the current item to ensure that it fits within the overall space. Does that seem right or do I not need to worry about

Hello @jim, Regarding this tweet of yours: whilst I generally share the sentiment of not tying up code to the platform, I’m sometimes struggling when it comes to practice. 1) When using Hilt,

hiltViewModel()

is the only “easy” way to get dagger-managed objects from within a

@Composable

function. Are there any alternatives? 2) In a non 100% compose app (where we can’t just disable all configuration changes in the manifest) any operation running inside a

rememberCoroutineScope()

will be interrupted during a configuration change. In these cases we need to resort to the `ViewModel`’s

viewModelScope

. Are there any alternatives? Any insight on the topic is very much appreciated!

I am trying to observe the total scrollY of a nested scroll connection, but the results are wrong for fast scrolls, code in 🧵

Do we have an option of manual storing and restoring component state like focus, list current index? There is problem when component is rendered conditionally

if(state.loading) {

ShowLoading()

} else {

LazyColumn{}

}

Hi everybody how are you ? I have a problem with a mutableStateFlow, when opening another composable it is always being invoked many times this is my code in case you can help me I have been researching for a long time ViewModel

private val _marketStatusIsClosed = MutableStateFlow(MarketStatusUiState())
val marketStatusClosed: StateFlow<MarketStatusUiState> get() = _marketStatusIsClosed

Composable

val marketStatusState by rememberFlowWithLifecycle(tickerDetailViewModel.marketStatusClosed)
    .collectAsState(MarketStatusUiState())

this is the code that is always running even though it is not visible to the user

if (!marketStatusState.isLoading) {
    Log.e("BuyInSharesScreen", "$marketStatusState")
    if (marketStatusState.isMarketClose) {

    } else {
        open another composable
    }
}

the new composable (screen) is being opened many times, and it is already closing so I do the navigation

currentBackStackEntry?.arguments?.putParcelable(CREATE_ORDER_INFO, operation)
navigate(Screens.BuyStockConfirmationScreen.route)

Hi all, what’s a good upper limit for # of parameters for a Composable (incl ones with default values)?

Would anyone happen to know of a sample that implements Scaffold and a collapsible TopBar? Can't seem to find an example of it, and I'd prefer to keep my TopBar in the scaffolding similarly as done in the compose samples

Can someone please help me with this keyboard flickering issue? https://stackoverflow.com/questions/69844103/how-to-remove-keyboard-flicker-when-switching-between-textfields

Is this the gist on how to make a Checkbox with a Text label in compose?

var theValue by remember { mutableStateOf(false) }
val doSomething = { theValue = !theValue }
Row(modifier = Modifier.clickable { doSomething() }, verticalAlignment = CenterVertically) {
    Text(text = "Show this: ")
    Checkbox(checked = theValue, onCheckedChange = { doSomething() })
}

or is there something else to have the touch ripples not be independent depending if you click on the row vs the checkbox.

I'm using a Card, and have a composable inside the card that I'm offsetting on the y-axis (basically trying to draw outside of the card), but the card seems to clip it's children. Is it possible to opt out of that behavior for a card? Edit: I converted the Card to a Box and I still get the same clipped output. 🤔

I can't find EqualWeight as shown off by Doris on twitter. Has the api changed? I tried looking for EqualWeight on cs.android.com with only 1 hit (and its a python file?)

Given a Fragment with a

LazyColumn

inside a

ComposeView

, both wrapped in a View based

BottomNavigation

container hierarchy. Goal: I need to pass outside View based events, e.g.

onTabItemReselected

, from containing

BottomNavigationView

to the compose hierarchy, to let my

LazyList

scroll up, as the current tab is reselected. My cumbersome, but working approach now looks like this, I am wondering if there are better ways, to avoid those ViewModel round turns, only to dispatch the

scrollToTop

- Event Thanks - 👉 Code in thread🧵

Hey. Does anyone know how to implement this kind of sticky headers in Compose? Or advise from where I should start looking?

Hey - Any ideas on why the deploy preview and live literals wouldn't be working? Not sure if is a compose version problem / configuration. The Preview works, but the deploy/interactive/live litterals just dont show.

Having a formatter class that is expensive to instantiate but the function

fun format(number: Int): String

it uses then is side-effect free. Where would you use it with Compose? In the ViewModel and expose the State as String or in Compose? I intuitively would expose the number as state - and see the formatting as part of transforming the state to UI - so put it into the Compose part. How would you then get this class in Compose - if for performance reasons I’d usually inject it as

@Singleton

or

@Reusable

via dagger?

Is it possible to achieve view in background like in the attachment?

Hi guys, I keep getting

java.lang.IllegalArgumentException: Key was already used. If you are using LazyColumn/Row please make sure you provide a unique key for each item

. I am sure all the keys are unique and I even logged them to be sure. Also this happens when items are rapidly added to lazy column. Please find the sample code in the thread

Will editing 2 mutableState values "at the same time" result in 2 recompositions?

How does the merging mechanism in the testing works? Imagining I have a list of :

Row {
   Text()
   Checkbox(selected)
}

How can I guarantee that the

Row

gets the correct

semantics

of

selected

that inside the

material.Checkbox

? Is there a way it can inherit that status from the "children" ?

message has been deleted

Is it a bad idea to define a class contianing Composable functions to impose a type dependency?

Is anyone using compose on android with kotlin 1.6.0-RC and not running into this error?

java.lang.NoSuchMethodError: 'void org.jetbrains.kotlin.gradle.dsl.KotlinJvmOptions.setUseIR(boolean)'

How to get padding values(top, end..etc) from

PaddingValues

class? there is no

<http://paddingValues.top|paddingValues.top>

getter!