Skip to content

Remove the status line from the scanning panels - #1210

Merged
enaboapps merged 2 commits into
mainfrom
feat/1209-no-panel-status-line
Oct 26, 2026
Merged

enaboapps merged 2 commits into
mainfrom
feat/1209-no-panel-status-line

Conversation

@enaboapps

@enaboapps enaboapps commented Oct 26, 2026 •

Copy link
Copy Markdown
Contributor

Closes #1209

What changes

  • No status line. Menus, the keyboard and the mouse panel no longer draw the line across their top ("Letters · QWERTY · Select a row", "Movement · Select a row", and so on). The highlight already shows what Select will choose. Panels are one row shorter.
  • Messages float beside the panel. States that need attention still show, as a short HUD label as wide as the panel just above it, or below it when the panel is docked at the top: a failed action, waiting or paused, a repeating key or pointer move with its stop instruction, "Back to rows" / "Back to groups" while going back is offered, a mouse notice, "Suggestions updating", and a layout that could not be saved. The label moves with the panel when it avoids the pointer and disappears when the state clears. Failed menu actions keep the existing detailed error label from the workflow.
  • No suggestion count. The keyboard's note beside the old status line ("3 suggestions", "Prediction loading") is gone. An empty suggestion row still says why across the row, as before.
  • scanning_status and item_status are removed; back_status stays for the going-back message.

One side effect to know about: while a switch is held and the hold-action prompt is showing, a panel message is hidden like any other HUD label, and returns on release. During a repeating key or pointer move the press is consumed as the stop, so that message is unaffected.

Docs

Home menu, keyboard and mouse panel pages each gain a sentence saying nothing is written across the panel and where messages appear.

Validation

  • cargo fmt, cargo clippy --all-targets -- -D warnings, cargo test (835 passed, 5 ignored)
  • npm run prediction-model, npm run lint, npm test (309 + 19 passed), npm run build
  • site: npm run build
  • Rendered the native keyboard and mouse panels with export_panel_size_fixtures on Windows and checked the PNGs: menu bar, then keys, nothing between.

🤖 Generated with Claude Code

Every panel drew a line across its top saying which page was open and
whether Select would choose a row, a group or a key. The highlight
already shows that, so the line is gone and panels are a row shorter.
What still needs the user's attention (a failed action, a pause or wait,
a repeating key or pointer move with its stop instruction, going back
to rows or groups, a layout that could not be saved) floats as a short
HUD label just above the panel, or below it when the panel is docked at
the top, and moves with the panel when it avoids the pointer. The note
counting suggestions is gone too; an empty suggestion row still says
why across the row.

Closes #1209

Co-Authored-By: Claude Fable 5.1 <[email protected]>
@enaboapps enaboapps added this to the v1.2.0 milestone Oct 26, 2026
@vercel

vercel Bot commented Oct 26, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
site Ready Ready Preview Oct 26, 2026 8:40pm UTC

Request Review

…he workflow

The overlay hosts draw a one-line prompt 64 logical pixels tall whatever
the rect says, so the panel message uses that height and keeps its gap
above the panel. A failed menu action adds no message of its own: the
workflow already shows the error, with what went wrong, beside the panel.

Co-Authored-By: Claude Fable 5.1 <[email protected]>
@enaboapps
enaboapps marked this pull request as ready for review October 26, 2026 20:43
@enaboapps
enaboapps merged commit 52b6220 into main Oct 26, 2026
10 checks passed
@enaboapps
enaboapps deleted the feat/1209-no-panel-status-line branch October 26, 2026 21:41

This branch was successfully deployed

1 active deployment
Preview — ef68d774 Deployed Oct 26, 2026 by vercel[bot]
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.

Remove the status line from the scanning panels

2 participants