Workaround for partial draw and initial window resize #20
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
|
Sorry for the late reply. Looks good but I'll play around with it this weekend before merging. Thank you very much! EDIT: I'll fix the CI, too. |
erikgeiser
reviewed
Jun 6, 2023
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.
When the initial
tea.WindowSizeMsgmessage comes in there seems to be some wonkyness in how bubbletea chooses to redraw the screen.After Init() the screen is drawn and then the WindowSizeMsg is returned asyncronously and seems to improperly update the screen with the new details. This sends a
ClearScrollAreamessage to force redrawing the entire screen.This is a workaround and probably isn't a proper fix (you do see a flash as the update message comes in)
Fixes: #18