Add independent load and send controls through the mapping window #7

Open
opened 2026-11-18 17:54:36 +01:00 by Dandaedre · 0 comments
Owner

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.html as the starting point.

Proposed workflow

  • Select an editor layer to see its load source and send destinations.
  • Choose one load source: connection → screen → layer.
  • Add one or more send destinations, each specifying connection → screen → layer.
  • Offer Follow load source for the familiar workflow: load from and send to the same device layer.
  • Give each destination a Send options control for choosing which properties to transfer.

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:

  • Position
  • Size
  • Crop
  • Layer fit
  • Mask / blanking
  • Input routing

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

  • Make load direction and send direction immediately distinguishable.
  • Support one load source and multiple send destinations per editor layer.
  • Keep common single-destination mapping quick and understandable.
  • Show readable device, screen and layer names alongside identifiers.
  • Clearly identify unavailable destinations and conflicting mappings.
  • Editing or selecting mappings must never trigger device operations.
  • Preserve fresh-state validation, conflict review and explicit send actions.
  • Define how device geometry is interpreted when loading from a different source than the send destinations.
  • Preserve mappings and send options through save/reopen, recovery, undo and supported embedded project snapshots.
  • Migrate existing projects to equivalent mappings and transfer behavior.
  • Keep the visual mock separate from production logic until its workflow is reviewed.

Acceptance criteria

  • Load an editor layer from one device layer and send it to another.
  • Send one editor layer to multiple layers across different screens.
  • Verify that each destination receives only its enabled properties.
  • Verify that input routing never changes unless explicitly enabled.
  • Switching back to Follow load source produces a clear, predictable mapping.
  • Disconnected, missing or conflicting destinations produce actionable feedback without silent reassignment.
  • Project and supported exchange round trips retain mappings and send options.
  • Existing single-destination projects retain their behavior.
  • Update the manual, persistence contracts, translations and relevant regression tests.

Out of scope: simultaneous multi-connection support and multiple project screens. This window should leave room for both without requiring their implementation.

## 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.html` as the starting point. ## Proposed workflow - Select an editor layer to see its load source and send destinations. - Choose one **load source**: connection → screen → layer. - Add one or more **send destinations**, each specifying connection → screen → layer. - Offer **Follow load source** for the familiar workflow: load from and send to the same device layer. - Give each destination a **Send options** control for choosing which properties to transfer. 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: - [ ] Position - [ ] Size - [ ] Crop - [ ] Layer fit - [ ] Mask / blanking - [ ] Input routing 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 - [ ] Make load direction and send direction immediately distinguishable. - [ ] Support one load source and multiple send destinations per editor layer. - [ ] Keep common single-destination mapping quick and understandable. - [ ] Show readable device, screen and layer names alongside identifiers. - [ ] Clearly identify unavailable destinations and conflicting mappings. - [ ] Editing or selecting mappings must never trigger device operations. - [ ] Preserve fresh-state validation, conflict review and explicit send actions. - [ ] Define how device geometry is interpreted when loading from a different source than the send destinations. - [ ] Preserve mappings and send options through save/reopen, recovery, undo and supported embedded project snapshots. - [ ] Migrate existing projects to equivalent mappings and transfer behavior. - [ ] Keep the visual mock separate from production logic until its workflow is reviewed. ## Acceptance criteria - [ ] Load an editor layer from one device layer and send it to another. - [ ] Send one editor layer to multiple layers across different screens. - [ ] Verify that each destination receives only its enabled properties. - [ ] Verify that input routing never changes unless explicitly enabled. - [ ] Switching back to Follow load source produces a clear, predictable mapping. - [ ] Disconnected, missing or conflicting destinations produce actionable feedback without silent reassignment. - [ ] Project and supported exchange round trips retain mappings and send options. - [ ] Existing single-destination projects retain their behavior. - [ ] Update the manual, persistence contracts, translations and relevant regression tests. **Out of scope:** simultaneous multi-connection support and multiple project screens. This window should leave room for both without requiring their implementation.
Dandaedre added the
enhancement
label 2026-11-18 17:54:36 +01:00
Dandaedre self-assigned this 2026-11-18 17:54:36 +01:00
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: idle-org/canvas-pilot#7
No description provided.