Record where a linear DNG too large for one texture goes

ARCH §5.3 still described only a tile cache nobody built; it now says what 0.19.0 tiles and what it does not: a linear DNG past PROXY_EDGE opens on a reduced copy, a finer render samples a full-resolution window, and the export is cut into halo-grown tiles. display-and- extension.md's FR-DSP-2 row said absent, outstanding.md said the halo had nothing to read it and that such a file fell to the embedded preview. rawler now builds from third_party, which ARCH's stack table and §3.2, the root Cargo.toml's comment ("two upstream crates ... for Android") and third_party/README.md's bump procedure did not know; the README also names each vendored crate's licence. panorama.md and the manual say a composite this wide develops and exports.
2026-09-27 19:42:42 -04:00
parent 6c749b469d
commit 4bd8d86c00
7 changed files with 67 additions and 20 deletions
@@ -351,6 +351,11 @@ it to bring it back. A frame that cannot be placed is named there with why,
 and `Merge` stays off until it is unticked. Blown sky stays white in the
 preview and in the composite.

+A panorama is usually far wider than a graphics card can draw in one piece.
+It opens in develop all the same, on a reduced copy that is drawn from the
+full resolution wherever you zoom in, and it exports at full size. The same
+goes for a panorama Lightroom stitched and saved as a DNG.
+
 ![Twelve frames aligned, the projections tried, and the border filled](media/panorama.gif)

 ![The alignment on a cylinder, each frame outlined where it landed](media/panorama-aligned.png)