A modern programming language that makes developers happier.

kotlinlang

What would be a performative way of synchronizing the scroll of two lazy columns? (yep, it has to be two different lazy columns, not a lazy grid)

If the answer is no, then the follow up question is what is synchronized scroll

no, but their elements have the same size and spacing

Can you guarantee that they load the content at the same time as well? Specifically, during very fast scrolls down the content stream.

I'd say yes, they do share the same object as state content

I'm wondering if building a custom lazy layout can help me with that

At some point you’d find yourself reimplementing the lazy grid

So to push back on the “has to be two different columns”, is there a specific limitation of grid that is an absolute blocker?

I'm actually applying a render effect in one lazy column and not in the other. Because the effect must be in the whole lazy column and not individual elements, the constraint arised

Can you crop the render effect to only apply to half of its content?

Eg i think you could use a chained shader to do that 

I'm gonna need to think about the implications in the application tho, but it looks like the right solution for me: single lazy column, but a more complex render effect

but I confess it's gonna be hard for me. The lazy columns intercept themselves with a "non flat" superposition, and I don't think I have the necessary skills to achieve that. Either way, I'm gonna be thinking about it

I’m very curious what sort of quantum app you’re building :stuck_out_tongue:

It’s hard to give concrete advice for a nebulously “described” problem

agreed, it's best to summarize it as synchronizing two "identical" lazy columns

yep, that's why the question's intent is about performative ways of doing so. Performance is the issue, I do have a solution what works, but not that great. The render effect topic arised from "is there a specific limitation of grid that is an absolute blocker?" which I was explaining about

Render effects can be applied on arbitrary parts of the content with chained / child shaders. But again, it’s not quite productive to talk about possible solutions without understanding the problem. You are trying to steer this in the direction of a very specific solution, and that falls exactly under the linked XY thing.

well, the discussion became unproductive :disappointed:. Unfortunately, for my skills, to do X is way harder than doing Y. And due to the limitations of what I can share, I'm blocked from exposing what exactly is X. And that's why, I hide the X details, and focus on Y. But anyways, I think its good for me, I'm gonna continue to research for the solution. Thanks for the hints though, I've found them productive