Add independent load and send controls through the mapping window #7
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Implement a mapping window that lets each editor layer load its layout from one device layer and send changes to one or more destinations.
The underlying mappings already separate loading from sending, but the current interface keeps them synchronized. This issue brings that flexibility into the GUI, using
docs/development/design/mapping-window.htmlas the starting point.Proposed workflow
Initially, connection selection can use the current connection only. The design should accommodate multiple connections later without implying that they are already supported.
Send options
Allow independent selection of:
Default to the existing layout-transfer behavior. Input routing must remain opt-in. Shared device input processing belongs in Input settings and is outside these options.
Unchecked properties must remain unchanged on the device, including during conflict resolution or forced sends. Explain or validate dependencies between size, crop and fit rather than silently enabling additional writes.
Requirements
Acceptance criteria
Out of scope: simultaneous multi-connection support and multiple project screens. This window should leave room for both without requiring their implementation.