Adam Brown
01/29/2023, 1:33 AMremembers
of screen A's composable. So when I pop screen B off the stack, screen A has lost where it was scrolled to in it's list. I think the strict compose answer to this is state hoisting. Something about that feels a little weird, but I suppose it can make sense?Adam Brown
01/29/2023, 1:33 AMstate
object, but that is multiplatform and shouldn't have any knowledge of compose
specifics.Adam Brown
01/29/2023, 1:34 AMViewModel
as that will survive the navigationAdam Brown
01/29/2023, 1:34 AMAdam Brown
01/29/2023, 1:35 AMArkadii Ivanov
01/29/2023, 1:49 AMremember
is lost whenever the Composable leaves the composition, which happens on screen switch. However rememberSaveable
should be automatically preserved if you use the Children
function. LazyColumn
should preserve its scroll state automatically as well.Adam Brown
01/29/2023, 1:50 AMArkadii Ivanov
01/29/2023, 1:50 AMAdam Brown
01/29/2023, 2:42 AMChildren
lost it's stateArkadii Ivanov
01/29/2023, 10:26 AMmovableContentOf
. I will try to play with it again.Adam Brown
01/29/2023, 8:38 PMBoxWithConstraints
and some mathAdam Brown
01/29/2023, 8:38 PMArkadii Ivanov
01/29/2023, 8:51 PM