Repository navigation
Use Textual's own flush callback for frame drawing - #513
Merged
Merged
Conversation
trissim
marked this pull request as ready for review
October 7, 2026 06:54
trissim
changed the title
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.
Codex work, mostly replaced. 2 of 13 code lines it added are still in main.
Remove the
FrameFlushdriver family fromframe_presentation.py. The frame code now calls the driver'scall_after_flushdirectly, relying on the Textual driver to run the callback after its write. Three small test and performance-tool files are updated to match.