Which chord should fire the playtest capture? nf-er1q ← Beads

closed priority 2 task unassigned needs:direction

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

Direction question from #356 (PR #362). The default ships if unanswered — this is only about whether the chord feels right in your hands.

Every controller button in tonapse is already bound, so the chord had to be picked for what its *halves* do, not just for being hard to fumble.

Option A — hold Back (Select), press Start. ← recommended, implemented today Start alone opens the menu, but its binding lives in _UnhandledInput, so the journal's _Input runs first and consumes the completing press — the menu never opens. Order is fixed (Start-first would open the menu before the chord completed). *Seam:* Back's own binding auditions the roll cursor's pitch (#167) while held, so capturing inside the piano roll plays a brief note. Suppressing that globally would break the feature.

Option B — L3 + R3 (both stick clicks). The familiar console screenshot chord. *Seam is worse:* L3 alone homes the roll cursor (#173) and R3 alone resets a focused dial (#323), so the first half fires a real side effect before the second lands — including one that changes a value.

Option C — something else. A dedicated Share/Capture button (Misc1) exists on DualSense/Xbox pads and is unbound here, but isn't on every controller and Steam often grabs it.

KVM mirror is F12 in all cases.

If A's roll-audition seam annoys you in practice, say so and I'll switch — the chord is one method (IsCaptureChord).

Dependencies

None.

Comments

No comments.

Add a comment