Add per-destination send options to mapping mockup

This commit is contained in:
Dandaedre 2026-11-18 15:41:13 +01:00
parent b686cdb3ea
commit 4b411aa020
5 changed files with 87 additions and 3 deletions

2
Cargo.lock generated
View File

@ -602,7 +602,7 @@ dependencies = [
[[package]]
name = "canvas-pilot"
version = "0.9.64"
version = "0.9.65"
dependencies = [
"base64 0.22.1",
"craft-dwg",

View File

@ -4,7 +4,7 @@ default-members = ["crates/canvas-pilot"]
resolver = "3"
[workspace.package]
version = "0.9.64"
version = "0.9.65"
edition = "2024"
license = "MIT"
repository = "https://proxy.dandaedre.com/gitea/idle-org/canvas-pilot"

View File

@ -4,6 +4,13 @@
## Unreleased
### v0.9.65
- Added per-destination **Send options** to the mapping window mockup: Position,
Size, Crop, Fit mode, Mask and opt-in Input. This is a visual proposal only;
application transfer behavior and save formats are unchanged.
### v0.9.64
- Source properties can stage a physical input with **Change input**, applied only

File diff suppressed because one or more lines are too long

View File

@ -37,6 +37,29 @@ The list shows small source/target counts so a layer with no routes or several
destinations is easy to spot. It deliberately avoids a large checkbox matrix:
connection × screen × layer combinations would quickly overwhelm that layout.
## Send options per destination
Each destination has a collapsed **Send options** control with independent
checkboxes for **Position**, **Size**, **Crop**, **Fit mode**, **Mask**, and
**Input**. Position and size are separate so an operator can move a layer without
intentionally replacing its dimensions. Crop includes edges, zoom and offsets;
fit mode is separate from that framing. Input means the destination’s video
source, not shared input processing settings.
The proposed default includes layout properties but leaves **Input unchecked**.
Unchecked properties should keep their current device values; all unchecked
should skip that destination. Following the load source should only link the
destination address, not these checkboxes. Other destinations retain their own
choices. In this mockup, controls only expand/collapse and toggle locally; nothing
is saved or sent, and sample counts do not change.
Before implementation, resolve geometric dependencies: device crop, fit, size
and position can affect one another. Preparation must use fresh device values
for excluded properties and explain or reject combinations that cannot preserve
them faithfully. It must not silently enable extra categories. The final transfer
review should show included properties and explicitly flag input changes.
This is a design proposal, not a promise of independent device fields.
## Questions for visual review
- Is the selected-layer approach comfortable, or is a project-wide route overview