-
Notifications
You must be signed in to change notification settings - Fork 1
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
Optimized Rendering #6
Comments
The use of |
Currently, animation frames are being injected into the signal queue as signals. Rendering to the DOM (via React or otherwise) only occurs when there has been a change of state, but the machinery that precedes that final render is being executed on every animation frame, at significant processor cost (see #13). |
Rendering should be triggered on the next animation frame, only by the following conditions:
The mechanism that manages requests for animation frames will have to be accessible to both the state accessors (setter) and the animation helper(s). |
The goal of this optimization is to ensure that rendering is not triggered more often than once per animation frame, regardless of the timing of signals and action execution.
The text was updated successfully, but these errors were encountered: