Does anyone know where this falls in the roadmap? ...

# compose

[brandonmcansh]

Does anyone know where this falls in the roadmap? https://issuetracker.google.com/issues/193263965

[Colton Idle]

Someone added a comment

Fixing this requires a big refactor of LazyVerticalGrid & its underlying implementation, which is planned for later this year.

[brandonmcansh]

oh nice

[brandonmcansh]

thanks for the heads up

[brandonmcansh]

well thats unfortunate

[brandonmcansh]

now to see if I can wrap a recyclerview in an AndroidView() and use my Compose GridItem

[Colton Idle]

Can you just use a different item at each of those indexes where you want to alter the z-index? and then just have two different item/composables?

[Colton Idle]

feels like there has to be a "workaround" or slight of hand trick you can pull here instead of going for a RV

[brandonmcansh]

yeah thats what im hoping for as well

[brandonmcansh]

trying to replace core feature of app in with compose

[brandonmcansh]

first roadblock ive hit so far (for this screen)

[brandonmcansh]

Can you just use a different item at each of those indexes where you want to alter the z-index? and then just have two different item/composables?

so basically add a single composable above the item being moved, and set the other one to invisible for the effect?

[brandonmcansh]

interesting, don’t know how well that would work for when dragging to items currently non visible

[Tin Tran]

Maybe calculate your items and split them into multiple rows and wrap them inside a LazyColumn?

[brandonmcansh]

yeah playing w/ a flow row idea

[Tin Tran]

There is a flow row in Accompanist you can try it

[brandonmcansh]

yep

[brandonmcansh]

thanks!

[brandonmcansh]

Couldn’t get flow route to cooperate but was able to get it working with a RV in an AndroidView using the composable VH