fabi/Sylpheed
1
0
Fork 0
Code Issues 9 Pull Requests Actions Packages Projects Releases Wiki Activity

re: the main menu remembers its cursor across menu -> title -> menu

Browse Source 
F1 TUTORIAL, two delivery-confirmed DOWNs to EXTRAS, B to the title, A back:
F3 is EXTRAS. Re-entry restores the item you left.

Reframes the initial-focus disagreement rather than settling it: if focus
persists, any 'initial focus' reading not taken on a fresh boot's first menu entry
measures history. It still says nothing about what the menu opens on -- this run's
F1 was itself carried over from a prior probe's press.

Reached on the plate-pulse gate, not boot_menu.sh, whose stillness test cannot fire
on this title -- TITLE at 422.7 s on a boot skip_intro could not gate at all.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Wuu56cE8vJGTBtn1ppsk8v
This commit is contained in:
sylph-decoder
2026-08-30 21:29:01 +00:00
parent a89406cebe
commit 8bcb1d1976
6 changed files with 344 additions and 58 deletions
Download Patch File Download Diff File Expand all files Collapse all files

24
docs/re/menu-navigation-semantics.md
View File

@@ -30,6 +30,30 @@ with [`tools/re-capture/menu_focus.py`](../../tools/re-capture/menu_focus.py).
Wrap holds on both screens tested — the 5-item main menu and the 3-item `EXTRAS`
submenu — so it is a menu rule, not a per-screen table.
## ✅ 2026-08-30 — the menu REMEMBERS its cursor across menu → title → menu
**measured** — [`data/focus-persists-across-title.txt`](data/focus-persists-across-title.txt),
`tools/re-capture/focus_persistence.py`. One run, control passed:
| step | focus | ring vector |
|---|---|---|
| F1, on the menu | `TUTORIAL` | 130 76 **254** 69 64 |
| F2, after 2× DOWN (**both delivery-confirmed**) | `EXTRAS` | 130 76 66 69 **254** |
| F3, after Ⓑ → title → Ⓐ → menu | **`EXTRAS`** | 130 76 66 69 **254** |
**F3 == F2, so focus persists** — the menu is re-entered on the item you left,
not on a fixed one.
📌 **And this reframes the disagreement below rather than settling it.** If focus
persists, then *any* "initial focus" reading not taken on a fresh boot's **first**
menu entry is measuring history. The records need not disagree about the game at
all — they may differ in what the cursor had already been moved to. **Nothing here
says what the menu opens on**; this run's F1 was itself carried over from a prior
probe's press.
⚠️ Reach: one boot, one round trip, one direction. Persistence across a **reboot**
is untested, and is the reading that would matter for authoring a default.
⚠️ **2026-08-30 — and the sources DISAGREE, which nothing here had noticed.**
`boot_menu.sh`'s own closing line says *"AT MAIN MENU (cursor on NEW GAME)"*, and
[`menu-state-in-memory.md`](menu-state-in-memory.md)'s run reaches `EXTRAS` in