Document two deferred Midra export sizing strategies

This commit is contained in:
Dandaedre 2026-11-13 14:13:04 +01:00
parent 32ea37f06f
commit 052a7cdaa8
2 changed files with 37 additions and 0 deletions

View File

@ -327,6 +327,36 @@ Gate: maintain several local layout alternatives, map them explicitly in Options
then export one named layer or exactly the visible set without changing local
geometry, overwriting a conflicting destination silently, or contacting a device.
### 12. Deferred: two Midra export sizing strategies
Status: backlog only, explicitly requested for later. Do not implement either
algorithm or change the current offline calculations for this task. Device
mapping remains unverified; this does not authorize any live-device calls.
- [ ] Add an explicit export strategy choice with two distinct sizing algorithms:
- **Output-sized layer:** set the Midra layer size to the desired final output
box, then calculate the internal crop needed to reproduce its size, crop zoom
and content offset.
- **Fixed-format input:** set the Midra input to a specified size/format (likely
16:9), then derive the sizing and crop needed to reproduce the desired final
output box, crop zoom and content offset.
- [ ] Design and validate each algorithm independently. Do not assume that the
same size/crop formula or device fields can serve both strategies. Both must
reproduce the same local visible bounds and retained content.
- [ ] Verify what "input size" controls in the target firmware, the order of
sizing versus cropping, crop units, aspect behavior, and any required position
correction for each strategy. Keep these hardware assumptions separate from
the offline document model.
- [ ] Include the strategy, requested final box, required device dimensions and
crop values in the export preview. Preserve the user's local geometry and crop
intent when switching export strategies.
- [ ] Add separate regression cases for both algorithms: changed aspect ratios,
custom input sizes, centered and offset crops, zoom, and pixel rounding. Verify
equivalent final bounds/content and report unsupported combinations explicitly.
Gate: two independently validated device mappings for the same intended visual
result, before either is used by the future export/API workflow in step 10.
## Coordinate contract to verify
Proposed internal model: screen origin at its top-left, X increases rightward,

View File

@ -191,6 +191,13 @@ crop on each vertical side. The retained native region is 600 × 500, scaled by
## Device mapping: keep the container separate
Deferred requirement: support both an **output-sized Midra layer with internal
cropping** and a **specified-format Midra input (likely 16:9) with derived sizing
and cropping**. These require distinct export algorithms; neither is implemented
or validated by the current provisional calculations. See
[the two-strategy export backlog](midra-layout-plan.md#12-deferred-two-midra-export-sizing-strategies).
The intended hardware aspect choice is **Centered**, as requested. The
[Analog Way Midra 4K V3.2 manual, pp. 66 and 87](https://www.bhphotovideo.com/lit_files/1168243.pdf#page=87)
describes input crops in pixels and layer cropping with resizing, with a separate