fix: this.delay not being respected with nonRealtimeData: true
#137
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The issue is noticeable at `millisPerPixel` being between ~ 0.5 & 2.0 the size of `requestAnimationFrame` period. Canvas image update period would be inconsistent - some would last longer, some less, some would get skipped altogether.
and when the user calls `render` manually with a custom `time` argument
WofWca
force-pushed
the
fix-delay-for-custom-render-time
branch
from
754047f
to
bc27bb2
Compare
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
and when the user calls
rendermanually with a customtimeargumentTODO:
nonRealtimeDatathat there is no delay, and if you're manually callingrender()with custom time that you've also factored the delay you want into thetimeargument.