Improve result pane scroll responsiveness - #23
Open
BeLeap wants to merge 1 commit into
Open
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
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.
Motivation
j/kfelt laggy because the UI only processed one input event per 100ms tick and used a bounded action channel that could become a bottleneck for repeated keypresses.Description
src/ui/manager.rsto avoid blocking on repeated keypresses.100msto16msinsrc/ui/manager.rsto reduce perceived input latency.pollcheck with awhile poll(...)loop insrc/ui/manager.rsso held/repeated keys are handled promptly.journal/2026-03-18/fix_scroll_lag.mddocumenting the investigation, root cause, and fix approach.Testing
cargo test, which completed successfully (no failing tests).cargo check, which completed successfully (build passed checks).Codex Task