Skip to content

Allow explicit keyboard text entry while configuring switches - #832

Merged
enaboapps merged 5 commits into
mainfrom
codex/switch-name-entry-823
Sep 21, 2026
Merged

enaboapps merged 5 commits into
mainfrom
codex/switch-name-entry-823

Conversation

@enaboapps

@enaboapps enaboapps commented Sep 21, 2026 •

Copy link
Copy Markdown
Contributor

Mapped keys can now be temporarily released through an explicit Type with keyboard mode. Focus alone never disables switch access. Closing or deleting the editor restores normal capture.

Validation: lint/build, 170 frontend tests plus 5 feed tests, Rust formatting/Clippy, 510 Rust unit tests and 7 integration tests passed; one existing test ignored. Independent review passed at 0b2e4f6. GitHub CI passed on Windows and macOS. The combined Windows ARM64 build passed native mapped-Space typing in existing and new switch names, Done/navigation cleanup, and exclusion with practice mode.

Closes #823.

enaboapps and others added 3 commits September 21, 2026 17:26
Keep keyboard-entry and remote-preset switch tests after remote presets landed on main.

Co-authored-by: Cursor <cursoragent@cursor.com>
@enaboapps
enaboapps merged commit fe67670 into main Sep 21, 2026
6 checks passed
@enaboapps
enaboapps deleted the codex/switch-name-entry-823 branch September 22, 2026 09:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Prevent mapped switch keys from blocking switch-name entry

1 participant