Or maybe we only have

withSave()

?

Any more ideas? The layout is more complicated than the sample one. I can convert it to Rows and Cols, but it'll be nice to know how to deal with "constrainedWidth" 🙂

Hi Compose guys! would it not make sense that for

StateFlow.collectAsState()

a

Dispatcher.Main.immediate

is used as default instead of

Dispatcher.Main

?

I’ve ran into an interesting case! I have the following composable

@Composable
fun CalculatorScreen() {

    val calculatorState by state { CalculatorState() }

    Column {

        CalculatorResultsRow(Calculator.calculate(calculatorState))

        VerticalScroller {
            Column {
                SliderFieldView(
                    field = SliderField.NUMBER_OF_BALLS,
                    onValueChanged = { calculatorState.numberOfBalls = it })
                SliderFieldView(
                    field = SliderField.WEIGHT_PER_BALL,
                    onValueChanged = { calculatorState.weightPerBall = it })
                SliderFieldView(
                    field = SliderField.WATER,
                    onValueChanged = { calculatorState.water = it })
                SliderFieldView(
                    field = SliderField.SALT,
                    onValueChanged = { calculatorState.salt = it })
            }
        }


        OutlinedButton(onClick = { Log.d("CalculatorScreen", Calculator.calculate(calculatorState).toString())}, modifier =  Modifier.fillMaxWidth()) {
            Text(text = "Save")
        }
    }
}

I would have expected

CalculatorResultsRow

to get updated with the new values every time the state changes, but it is not the case. A change of value on

onValueChanged

doesn’t mean the tree is re-rendered? What am I missing?

Just a wild guess and question; when an attribute of the state (calculatorState) changes, can Compose know that it has changed?

Good question, I will try with 4 state values instead

@Siyamed You were right, Compose doesn’t look inside an object used as a state 😞

Leland and Adam would definitely know about it i am rusty there right now

The worst might be resetting the state

How would I do that?

calculator = calculator.copy(x=y) (Edited according to @Mark Murphy's answer)

yeah let’s not disturb them, I work on Sundays and it’s the evening anyway 😛

Is there any specific date when the first beta version of Compose will be released?

tbh, I'm really excited about Compose. It's going to revolutionize the way we create UI; almost after a decade of making it the traditional way.

@Mehdi Haghgoo We didn’t even give a specific date for the first alpha 😛

Compose is truly amazing, I am in owe. I work all day on a 9 years old app and the evening, I do some Compose (like right now) to feel better, and it scratches the spot perfectly!

You can put me on record as saying "When it's done + a few weeks to actually release it" 🙂

@galex are you migrating your old app codebase to Compose?

lol I wish, it’s wayyyy to early for that… you can’t put something in production without the library having been stamped stable aka 1.0…

Same as we would do in xml I suppose, so two it is if they are different, right?

@galex, that has to be two composables I guess, the way two composables are created for default and dark theme.

And @Leland Richardson [G] just posted a tweet about how a recent change to make the common layouts

Row

and

Column

inline functions had a huge performance benefit: https://twitter.com/intelligibabble/status/1285642262454640645?s=20

👀 JetNews bumped to dev15 and Kotlin 1.4 https://github.com/android/compose-samples/pull/112

Any idea / guesses as to what proportion of people who are playing with Compose are in this slack?

is animateContentSize modifier is included in dev15?

No, it just went in today I believe

So it should be in dev16

thanks

How can I keep my windowBackground transparent? Seems like at some point Compose takes over the window management and just fills it up like I didn’t set the following:

<item name="android:windowBackground">@android:color/transparent</item>
        <item name="android:windowIsTranslucent">true</item>