fix: timer block issue #31
Open
Conversation
This file contains hidden or 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
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.
This PR fixes the app-freezing issue that sometimes occurs. Turns out that the problem was way simpler than we initially thought. On each animation frame we send a
FrameMsgthat updates the slide which batches aFrameMsgalong with anotherTickMsg, on eachTickMsgsince we also update the globalTimer we send anotherTickMsgand this keeps going until the app halts.The fix is just to update both timers on the same
TickMsgand send only a single one back to bubbletea's event loop so there is only a singleTickMsg.