Hi lads, lasses, does anyone know why my Card insi...
# compose
p
Hi lads, lasses, does anyone know why my Card inside a lazyColumn loses its state after scrolling if I wrap its content with two Rows or Columns? As far as I understand, hoisting is holding values state on its "parent's scope" or where the Composable is being called. Here I attach two screenshots, the first one shows the lazyColumn and the Emulator's example with the double rows., the second one shows the listItem without double Rows. Both emulator examples are after scrolling. I was wrapping a Row inside another one, in order to use the .align modifier. Don't pay attention to the Greeting code since it was to clear some doubts, check if I was losing the state, or the problem was something else.
b
I have the same problem. A pretty straight forward LazyColumn that consists of
Row
composables, and each
Row
has several composables, including a
Column
composables. When the list is scrolled, the
Column
composables inside the row do not get rendered when scrolled onto the screen …
😓 1
c
beta08 has had issues with lazyCol. Don't know if it's related but search the past few days and you'll see a n issue tracker.
👍 1
a
@Patrick Duarte are you on beta07 or beta08?
b
i’m on beta08
p
@Andrey Kulikov I'm on JCompose beta07
Copy code
val compose_version by extra("1.0.0-beta07")
I'm updating the project right now, now that you asked
a
@Bradleycorn if you see this on beta08 could you please file a bug?
b
@Andrey Kulikov Sure thing.
p
Updated to compose beta08, Kotlin gradle 1.5.10 and a couple compose dependencies, now the mentioned issue is not present anymore.
Copy code
val compose_version by extra("1.0.0-beta08")
Thanks, I thought I had misunderstood something about Compose of what I've read so far. Here the screenshot after scrolling:
a
yes, this issue was fixed in beta08
👍 1