Stop the keyboard and mouse panel depending on other windows - #942
Merged
Merged
Conversation
The panels open and keep working with no window in front. A change of window no longer ends a panel or resets the keyboard's modifiers, Caps or highlight, and a change to the work area moves the keyboard to fit. What belongs to the text of one window is still let go. Closes #941 Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Review follow-up: every point scan now follows whichever window is in front, or none, until a switch is used in it, so a window coming forward as a panel closes no longer ends it. The wait for a window is gone with the need for it. The keyboard keeps its display by name, stays put while displays cannot be read, and a keyboard that fails to open from the mouse panel returns to the panel. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Review follow-up: a scan restarted by a change of mode follows the window like any other. A scan that follows is not checked against the window it has just taken up. The mouse panel stays where it is while displays cannot be read, as the keyboard does. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
The one-second wait described for automatic restart is gone. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
enaboapps
force-pushed
the
panels-independent
branch
from
September 28, 2026 12:07
7081dc8 to
c8dec25
Compare
enaboapps
marked this pull request as ready for review
September 28, 2026 12:07
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
2 participants
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.
Closes #941
Change
The scanning keyboard and the mouse panel no longer depend on other applications' windows.
Point scanning
Point scanning and its menus stay tied to the window in front, so a click cannot land on the wrong window. One thing changes, to make leaving a panel reliable:
Kept on purpose
These belong to the text of one window, and stop Switchify editing the wrong application:
Risk to be aware of
A locked Ctrl, Alt or Win now carries over when another window comes forward, so the next key is a shortcut there. The modifier overlay and the keyboard both show the locked state.
Validation at c8dec25
All run locally on Windows and passing:
npm run lint,npm test,npm run buildcargo fmt --checkcargo clippy --all-targets -- -D warningscargo test: 603 passedThe window and display handling runs in the native runtime. The decisions in it are unit tested: when a window change matters, and which display the keyboard belongs on. The order of the runtime's steps is not covered by automated tests. Not verified in the running app, on Windows or macOS.
🤖 Generated with Claude Code