fix: no tick with high accuracy #6
Open
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
Fix the ticker not firing if the accuracy so small the underlying ticker can't achieve the given accuracy. The ticker will now send a tick as soon as the target time is matched or has been passed. This changes the behaviour so it won't fire early even when within accuracy. Correct example to not use range as that will never end as we the channel is never closed. Fixes: Unity-Technologies#4
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.
Fix the ticker not firing if the accuracy so small the underlying ticker can't achieve the given accuracy.
The ticker will now send a tick as soon as the target time is matched or has been passed.
This changes the behaviour so it won't fire early even when within accuracy.
Fixes: #4