Fix app loading and event management in DisplayApp #1054
Merged
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
… the new one. This way, we ensure that lv_task_handler() is called before sending event to the newly loaded app.
Riksu9000
approved these changes
Mar 27, 2022
Contributor
Riksu9000
left a comment
Riksu9000
left a comment
There was a problem hiding this comment.
This function is only used in paint and paddle and both work perfectly.
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.
In display app, call the event handler of the current app before loading the new one. This way, we ensure that lv_task_refresh() is called before sending event to the newly loaded app.
Fix #1023