Help: Fn+h lists the keys of the screen you're on; no screen names its keys any more (#69) #73

2026-10-06T23:30:07Z

twisla commented

2026-10-06 23:30:07 +00:00

For #69: one help key everywhere, and no key hints on any screen (decisions Q196 to Q203, docs/milestones/U1.md).

What it does

Fn+h on any screen, text fields included, and ? outside Text Entry, open a panel over the content area: the keys of the screen you're on, then an "Everywhere" group. Arrows scroll; any other key closes it and is not passed to the App.
Every App declares its keys for the state it is in (App::help()): pages, viewers, dialogs and text fields answer for themselves. The App manager opens the panel and takes every key while it is open.
About 30 hint lines removed, from every App. Footers that remain show state only (REC 12 points, sort:signal, what is waiting to be pasted). Messages that named a key were reworded.
The first-start Setup keeps its hints (Q200) and teaches the key on its first and last screens. A device set up before gets one Toast, once. The user guide and the FAQ open with it.
key help over the consoles.

Checked: 476 host tests (8 new: the mapper, the panel, the App manager). On the device with key help and screenshots: the Launcher, all nine Apps, and several states (Storage scrolled, System's tasks, a Settings text field, Wi-Fi Tools' networks); the one-time Toast. Site: 68 pages, 0 problems. Costs 8.5 KB of flash and 40 bytes of static RAM.

Not checked:

The real Fn+h and ? on the keyboard. The mapper is host-tested and the device was driven with key help; please press them once.
The Setup screens: only a device that was never set up shows them, so their new text has not been seen on a screen (a line may wrap badly).
States that need something to happen first (dialogs, a copy in progress, a Gemini prompt, a packet's details): their lists were read against the key handling, not looked at.

Follow-up filed: #72, generating the website's key tables from the same lists.

🤖 Generated with Claude Code

https://claude.ai/code/session_01EhqxQ49eCju4CzKYNjZzwT

For #69: one help key everywhere, and no key hints on any screen (decisions Q196 to Q203, `docs/milestones/U1.md`). **What it does** - **Fn+h** on any screen, text fields included, and **`?`** outside Text Entry, open a panel over the content area: the keys of the screen you're on, then an "Everywhere" group. Arrows scroll; any other key closes it and is not passed to the App. - Every App declares its keys **for the state it is in** (`App::help()`): pages, viewers, dialogs and text fields answer for themselves. The App manager opens the panel and takes every key while it is open. - **About 30 hint lines removed**, from every App. Footers that remain show state only (`REC 12 points`, `sort:signal`, what is waiting to be pasted). Messages that named a key were reworded. - **The first-start Setup keeps its hints** (Q200) and teaches the key on its first and last screens. A device set up before gets one Toast, once. The user guide and the FAQ open with it. - `key help` over the consoles. **Checked:** 476 host tests (8 new: the mapper, the panel, the App manager). On the device with `key help` and screenshots: the Launcher, all nine Apps, and several states (Storage scrolled, System's tasks, a Settings text field, Wi-Fi Tools' networks); the one-time Toast. Site: 68 pages, 0 problems. Costs 8.5 KB of flash and 40 bytes of static RAM. **Not checked:** - **The real Fn+h and `?` on the keyboard.** The mapper is host-tested and the device was driven with `key help`; please press them once. - **The Setup screens**: only a device that was never set up shows them, so their new text has not been seen on a screen (a line may wrap badly). - States that need something to happen first (dialogs, a copy in progress, a Gemini prompt, a packet's details): their lists were read against the key handling, not looked at. Follow-up filed: #72, generating the website's key tables from the same lists. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01EhqxQ49eCju4CzKYNjZzwT

twisla added 1 commit 2026-10-06 23:30:08 +00:00

Help: Fn+h lists the keys of the screen you're on, and no screen names its keys any more (#69 )

Site / build (pull_request) Successful in 14s

Details

CI / build (pull_request) Successful in 7m22s

Details

7fe8b3d22a

Fn+h on any screen, text fields included, and ? outside Text Entry, open a
panel over the content area: the screen's own keys, then the ones that work
everywhere. Every App declares its keys for the state it is in (pages,
viewers, dialogs and text fields answer for themselves); the App manager
opens the panel and takes every key while it is open.

About 30 hint lines are gone, from every App. What stays on a screen is
state. The first-start Setup keeps its hints and teaches the key; a device
set up before gets one Toast, once. The guide and the FAQ open with it.
`key help` over the consoles.

476 host tests (8 new). Checked on the device with key help and screenshots:
the Launcher, all nine Apps and several of their states. 8.5 KB of flash and
40 bytes of static RAM. Decisions Q196 to Q203 in docs/milestones/U1.md.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01EhqxQ49eCju4CzKYNjZzwT

twisla merged commit 82023d36b3 into main

2026-10-06 23:38:50 +00:00

twisla referenced this pull request

2026-10-06 23:42:54 +00:00

Keys: one table file for the device's help panel and the website's key tables (#72) #75

twisla referenced this pull request

2026-10-06 23:47:36 +00:00

Help: one global shortcut that shows the current screen's key bindings, and no more hint lines #69

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: twisla/roro9stack#73