eygraber
02/23/2021, 6:48 AMremember
something mutable, but not cause a recomposition when it is mutated?lewis
02/23/2021, 6:57 AMremember {}
do this? If you don't pass it a key it just won't recalculate on recomposition?eygraber
02/23/2021, 7:04 AMjim
02/23/2021, 1:09 PMShakil Karim
02/23/2021, 6:22 PMjim
02/23/2021, 6:28 PMShakil Karim
02/23/2021, 6:35 PMeygraber
02/23/2021, 8:50 PMval previousHolder = remember { atomic(holder) }
so I can query the visibility state from the last time the container was updated.
I know the correct thing to do is probably to sent the previous state to the composable together with the new state, but it was 2 AM and this was working 😄
The main thing I needed was to not recompose immediately after "remembering" the visibility, because that messed with the animation.