[528z4b2kgc-ux]

Fix or feature

• Fix
• Feature

What and why

Problem. Swapping two touch controls, such as the left stick and A B X Y, is rejected, and both go back to their built-in places.
Cause. Moved controls are placed one at a time, so each waits for a place the other still holds.
Change. Placement tries all moved controls together first, then falls back to one at a time. The engine patch and the editor's TouchPadGeometry.swift change the same way.

Checked

• Tests: TouchLayoutTests passes; pad_geometry_check.m passes (14 screens, 10080 arrangements); python3 tools/engine.py check passes.
• Test for a fix: check_swap (engine) and theStickAndTheDiamondTradePlaces (editor). Both fail without the fix.
• Run on a device or Mac: iPhone Duo, in a fork build with the same change. The stick reached the bottom right once A B X Y was moved away.
• Not checked: other iPhones and iPads on a device.

Screenshots

None, no visible change.

Scope

• No engine file (dm/, scripts/, docs/, ref/) is added to the repository: a change there is a patch in patches/ (a commit in engine/, then tools/engine.py export, and tools/engine.py check passes), with its Upstream-Status
• A fix to the engine or a game profile also goes to seedds/nxnative as a PR in parallel: this PR's patch says forwarded seedds/nxnative#..., or pending until that PR is open
• A change to a launcher view has before and after screenshots above
• No keys, game files or data extracted from a game in the change or the attachments

Details

• The patch builds on 0020-ios-touch-controls-layout, which is not in seedds/nxnative yet (it builds on iOS: adapt gameplay to Duo portrait and tabletop poses seedds/nxnative#683). So there is no upstream file to send this to; the patch says pending with that note.
• If the together-first layout does not fit, the old one-at-a-time placement runs as before, so a layout that worked keeps its result.

🤖 Generated with Claude Code