CONTROLS panel: bigger glyphs, and the glyph-header card that pays for them nf-gl1l ← Beads

open priority 2 task unassigned

Twinned from https://github.com/cfsh/ninefold/issues/497 by tools/beads/import_github.py's reconcile pass.

Deferred from PR #455 by aedanpope: *"Bigger glyphs can be deferred to an issue."*

Two of his 2026-08-04 playtest items, which belong together:

Item 9 — glyphs could grow. *"the □ + R2 could be a little bigger, for example."* Today ControlsGuide.BadgePx = 24f, unscaled — measured at exactly 24px beside ~41px type in pr455/controls-panel-wider.png, so it is conspicuously the one element that did not scale.

#456 case 2, step 3 — the glyph-header card. From his answer on #456:

> "There's also more space than it seems because the words were getting crammed to the right of the glyphs — instead allow the glyphs to appear as a 'headerish' card and underneath is what the words are for those glyphs — only in cases when needed."

Note *"only in cases when needed"*: rows that fit keep the current side-by-side form, so the panel has to support both layouts per row rather than switching wholesale.

Why they are one issue

The panel's width budget is already spent. #455 shipped case 2 steps 1–2 (+50% width, then a per-word font shrink), and at one screen × 200% the guide is already elastic down to its collapsed width because the SONG header buttons alone take ~1500px of a 1920 viewport (#455 L1). Growing the glyphs now would push straight back into the state that was just fixed. The card reflow is what buys the room back — it is the reason step 3 exists.

So: card first, then glyphs, then confirm the size he means once a card layout exists.

Already in place to build on

Filed unclaimed.

Dependencies

None.

Comments

No comments.

Add a comment