Open
Conversation
Introduce the `sync_update` attribute to the Screen class to control synchronous screen updates. Changed `draw` into a property to ensure the refresh state is managed correctly when the draw value changes. Included timing measurements for refresh operations and conditional refresh triggering.
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
1 participant
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.
I made tests with enabling synchronous update mode for screen. This can be turned on with Screen.sync_update = True per Screen subclass.
This feature hooks into Widget class draw, which is changed into property and setting draw=True will also trigget screen refresh with Screen.rfsh_start.set()
Currently code includes test printouts and refreshing is tested only with Button class.
Do you think this would be good way to save resources and take screen refresh to control?