You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 25, 2018. It is now read-only.
Currently all properties are added/changed/removed from their respective nodes immediately. It can be better optimized by batching these changes together on animation frame.
Ideally the strategy should account for scenarios where multiple changes to single prop happen between animation frames. (e.g. if prop A was added and then removed, no action would be taken).
The text was updated successfully, but these errors were encountered:
Where do you recommend that functionality to exist? If you point me to the right critical point where vtree is redrawn, I'll look into making a throttle-by-frame behavior.
Context:
Currently all properties are added/changed/removed from their respective nodes immediately. It can be better optimized by batching these changes together on animation frame.
Ideally the strategy should account for scenarios where multiple changes to single prop happen between animation frames. (e.g. if prop A was added and then removed, no action would be taken).
The text was updated successfully, but these errors were encountered: