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

re: all four measured submenus reset -- the main menu is the only screen that remembers

Browse Source 
LOAD GAME, TUTORIAL and OPTIONS all reset on re-entry, joining EXTRAS. With the
main menu persisting, the rule is four of four submenus resetting and one
exception -- the opposite of what a single screen had suggested.

Fourth attempt, and every control in it is a previous failure: the decision uses
the cursor's own region so no per-screen geometry is assumed (sweep 1 read the main
menu's gutter on screens whose cursors are elsewhere); the back-on-the-menu test is
the narrow ring row (sweep 2 died when a crash dialog defeated whole-frame
comparison); absolute row checks after every press (a constant offset passes a
differential control); and a two-sided self-test that constructs both verdicts,
which had already caught a rule I broke myself.

Screens confirmed by eye and committed as evidence, because an earlier run was
fooled about which screen it was on. LOAD GAME's 21.6 is explained by its list
scrolling rather than moving a ring.

Still not separated: resets-to-named-item vs resets-to-top-item. None of these
three has an opening item that is not its first.

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-31 01:23:28 +00:00
parent 571d7e87b0
commit 4b8afbe85e
5 changed files with 127 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

30
docs/port/HANDOFF.md
View File

@@ -14,6 +14,36 @@ delivered.
## ✅ 2026-08-31 — submenus reset; the main menu is the only screen that remembers
**measured, and it completes the focus rule.** `LOAD GAME`, `TUTORIAL` and
`OPTIONS` all **RESET** on re-entry, joining `EXTRAS`. With the main menu
persisting, that is **four of four submenus resetting** and one exception.
| screen | verdict |
|---|---|
| `LOAD GAME`, `TUTORIAL`, `OPTIONS`, `EXTRAS` | **RESETS** |
| main menu | **PERSISTS** |
Your `guard_focus_scope` can move from *"two measured screens disagree, three
unmeasured"* to *"submenus reset, the main menu persists"* — but the guard is still
right to exist: it is measured per screen, not derived.
❔ **`NEW GAME` remains deliberately untested** — it starts a game.
❔ **And your MISSION-SELECT-vs-top-item question is still open.** None of these
three separates it: each opens on its own first item. `LOAD GAME` looked like a
counter-example — it opens on slot 01 with slots 19 and 20 drawn *above* — but that
is a wrapping list around a centred selection, and 01 is still first.
⚠️ Reach: one boot, one round trip per screen, one direction, one entry each. A
reset after a **reboot** is untested.
[data](../re/data/submenu-focus-all-reset.txt) ·
[TUTORIAL](../re/captures/menu-nav/live-tutorial-submenu.png) ·
[LOAD GAME](../re/captures/menu-nav/live-load-game-slots.png)
## ❔ 2026-08-30 — LOAD GAME, TUTORIAL and OPTIONS: still unmeasured, and why
**No new value here. This is a negative, so you know what I tried and what it