-
-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rerender / recalculate handle for the VList #481
Comments
Hello @Razum , const ref = useRef(null);
<VList
ref={ref}
onScroll={(offset)=> {
if (offset < 100) return ref.current.dontFixChildrenPosition();
ref.current.fixChildrenPosition()
}}
> |
Thanks, I understood. I think recalculate like method will not be suitable for virtua because of its architecture, but the idea is helpful. I'll try to think this hard problem again. |
The point is that virtua have to know where the items are removed from/added to, before modifying DOM on next render. Currently |
I would consider not just a flexible component that easily adapts to passed properties and flags, but rather a component that operates in different modes: standard and reverse. In standard mode, it would be , and in reverse mode, . Each mode operates with different strategies for size, offsets, and scroll calculations, as there are too many differences between them, but they use the same cache. Under the hood, these could be different Virtualizers. |
Hi @inokawa!
First of all, thank you for creating such a wonderful component.
I'm currently facing the same issue mentioned by @mattwondra here.
I've noticed that triggering a resize causes Vlist to recalculate its children's positions and fixes the layout. Since the shift issue seems to be more complex and requires significant effort, is it possible to add a recalculate handler to the VList?
Thanks in advance!
cc @LookRain
The text was updated successfully, but these errors were encountered: