Fixed
Status Update
Comments
da...@sonos.com <da...@sonos.com> #2
I proposed this which I think it is better than the actual behavior, and could let the developers work with more room to be creative.
https://code.google.com/p/android/issues/detail?id=58318
da...@sonos.com <da...@sonos.com> #3
The presentation link doesn't work.
an...@google.com <an...@google.com>
ap...@google.com <ap...@google.com> #4
In Custom Notification Layouts section of the Notification API Guides, it states: "The height available for a custom notification layout depends on the notification view. Normal view layouts are limited to 64 dp, and expanded view layouts are limited to 256 dp". I guess it means the width is 512 dp and the height is 256 dp (if following the 2:1 aspect ratio)?
http://developer.android.com/guide/topics/ui/notifiers/notifications.html#CustomNotification
as...@google.com <as...@google.com> #7
Any update on this?
Description
Jetpack Compose version: 1.3.0-beta01 Jetpack Compose component used: derivedStateOf Android Studio Build: Chipmunk Kotlin version: 1.7.10
From the documentation of
derivedStateOf
, it saysThe result of calculation will be cached in such a way that calling [State.value] repeatedly will not cause[calculation] to be executed multiple times
. This was true prior in Compose 1.2.0, but no longer is.Here is sample code to reproduce the issue:
The output in Compose 1.2.0 gives:
and in Compose 1.3.0-beta01 gives:
As you can see from this output, in Compose 1.2.0,
calculating zero state for scroll offset
only appears once every time the scroll state changes (as expected), and then the inner compositions recalculate their color accordingly. But in Compose 1.3.0-beta01,calculating zero state for scroll offset
shows up many times every time the scroll state changes. The number of times it runs increases with the number of composables that use its state.I'm pretty sure this was caused by https://issuetracker.google.com/issues/230168389