Arrange Keys: drag-to-reorder the key rail and visionOS cluster - #62
Merged
Conversation
jhen0409
force-pushed
the
arrange-keys
branch
2 times, most recently
from
August 27, 2026 06:45
2217040 to
5ef1e61
Compare
- ⋯ menu → Arrange Keys…: the keys wiggle and each is a system drag source; the move is the tab strip's UIDragInteraction/UIDropInteraction recipe, shared by the iPad rail and the visionOS cluster through one KeyBarDropCoordinator (nearest-key target, tab-cell highlight, displaced- neighbour landing). TerminalChromeDragPayload/TerminalChromeDragItem are the process-local item recipe tabs and keys now share; the pane's file gate refuses every chrome drag with one check. - The order is a slot permutation (KeyBarOrder, KeyBarOrderStore, device-local); rails reconcile it in layout, gaps and widths stay put. visionOS: a drop on the other slab crosses the UMD; the ARRANGE KEYS bar (RESET · DONE) is its own slab below the console row, one per tab. - visionOS: GUIDE moves from the console row into the ⋯ menu. - MultiplexUITests + `build.sh uitest` (XCUITest press-and-drag), unit tests with fake drop sessions on both platforms, docs and TestFlight notes.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
UIDragInteractionon eachTerminalTallyKeyControl,UIDropInteractiontargets whose delegate is one sharedKeyBarDropCoordinator(nearest other key by centre lights like a tab cell; landing parks the displaced keys for UIKit's drop animator). The rail (iPad/iPhone) and the visionOS cluster context adopt it throughKeyBarDropSurface.KeyBarOrder,KeyBarSlot— keyboard/mic share one slot, TMUX/HRDR another), stored device-local (KeyBarOrderStore); gaps and widths never move. Rails reconcile the order in layout (never part of the render signature), so a drop, RESET or a VoiceOver move re-creates no key.guideIsDirectChip, one decision for rows and menu).TerminalChromeDragPayload/TerminalChromeDragItem); the pane's file-drop gate refuses every chrome drag with one check; the tab strip's drop rule now runs through the same pureRowDropGeometry.Verification
build.sh build+ targeted unit suites green on visionOS and iPad (key control, rail/cluster incl. fakeUIDropSessiondrives of the coordinator, order model, UMD, window, pane, tab strip);build.sh lint0 violations;check-metadata.rbOK.build.sh uitest [vos|ipad]→MultiplexUITests/ArrangeKeysUITests: real-touch press-and-drag of ESC onto TAB passes on the final code (iPad Pro 11-inch (M5), iOS 26.4 simulator:escape control tab→control tab escape, RESET restores, DONE). The visionOS simulator cannot synthesize a lift for a drag interaction — the test skips the drag there.debug.arrangekeys,debug.arrangekeysmove): bar below the console row, a key carried across the UMD; console row shows GUIDE gone and ⋯ present.Notes