Is the ScalizingLazyListState() and ScalingLazyColumn autoCentering conflict still present in wear compose-material:1.0.0?
The following code doesn’t work, which shows only a dark screen at the beginning.
And set to (1, 0) as the both defaults are, doesn’t work. (0, 0) seems to be the only working combi. I think this issue was also present in horologist (https://github.com/google/horologist/issues/245).
Any thoughts on this are appreciated.Update: It is worth to mention that my items are two full screen elements. After I scrolled the screen, the code behaved like I had set (0, 0).
Thanks - will probably be Monday before I take a look - interesting that is it happening for
I don't have any immediate ideas why it would matter what the type of content is - but with a repro case I am sure we will soon get to the bottom of it.
I think I have found and fixed the problem, just need to do a bit more testing and a patch should land today. As a workaround add a 0.dp height spacer as a third item in your list and it should be visible as expected.
Also thanks for the great bug report - so much easier to find these issues when you have a good repro case.
1 month ago
Indeed the workaround adding a 0.dp height spacer as a third item in my ScalingLazyColumn works. 😇Thanks also for the rapid responses, I am glad that I can help make wear-compose rock solid.
1 month ago
cool - the patch will land in 1.0.1 and 1.1.0-alpha04 on 24th August as we missed the cut for this weeks release - but as we have a workaround hopefully that is not too inconvenient