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.
We have pretty solid scroll persistence when strictly appending, but I noticed it still gets wonky sometimes, and it turns out that's because we don't persist scroll position when deleting lines, etc. This PR refactors the way changes to the Buffer are passed onto the Renderer, by essentially having the Window subscribe to changes to the buffer.
JLineBuffer
now does nothing on its own (we keep it around just in case we need some renderer-specific bits in there) and insteadJudoBuffer
notifies any attachedIJudoWindow
instances that it's going to change something, and then that it has changed something, providing storage for the windows to save some state that they want handed back to them after the change.This allows
JLineWindow
to trigger rendering when any change in anyJudoBuffer
subclass occurs, and also to update its scroll position as necessary.