A dock drop's mark is DropMark::Region: the rect the moved panels take once
dropped, laid out from the layout after the drop by the functions the dock
draws with (tree frames, column cells, column group rects) in the room the
dock registered, pruned as the area shows it. A tab join adds its tab line; a
reorder in the own strip marks the line only. The ghost painter washes the
region with the drop rule's colour under the shared band. Region replaces
DropMark::Split; a spot without a placed rect marks a line along its edge.
A collapsed native window records its expanded rect, so expanding it restores
its size; an open OS window always carries its maximum size, so a lifted strip
limit reaches the OS; a viewport is sized within its own limits; a dock opens
OS windows only where its mount would, so a float over a full-screen window is
an in-app window that moves; a native window's edge is measured and recorded
in app coordinates. The floating window's title row shows the double arrow and
Close; its menu opens from the band.
A window a drag did not start in takes the desktop pointer while the drag runs, never the place it last saw the
pointer itself: the source window holds the pointer, and the window may have had no exit (a palette laid over it).
A floating dock window whose column has steps is sized by its caller in an OS window too (Resize::by_caller): the
OS window is not OS-resizable, the app runs its grips and reports each step, the dock turns the resize into whole
steps and sends the window their rect at once. The input hook's release of an OS resize applies only to windows
the OS may resize.
The pass that moves the pointer onto a row paints that row lit and the row it left unlit, with no
follow-up pass. Rows no longer activate themselves on hover; runtime::pointer::hovers reads the
pass's one resolution for a component. MenuItemOutput reports whether the row is active. Trial:
a pointer move over the rows of a scrolling menu, at 1x and 1.5x, down and up.
- craft-behavior: Preview<V> derives Default with #[default] Unchanged (clippy::derivable_impls on Rust 1.100).
- craft-prepress tests/flatten_write.rs: main's even-odd test needs the Cyan ink const.
- craft-svg: the embedded-SVG scene test needs the data-URL image resolver, which is behind feature tree.
- Docs: no links to private items (markdown, dwg, ui-patterns), no link to a crate that is not a dependency (frame), write() for the function (doc-binary), an autolink for the URL (update), Self::from_bytes (psd). craft-midi's source_timed and craft-pdf's cos::content keep only their inner docs, so their links resolve inside the module.
- README: main's craft-zip entry with its lenient reader sentence, lost in the 17 Nov merge.
The 17 Nov merge dropped is_artcraft_remote, oci_ref_available and remote_manages_flatpak (and their tests, as trials) with the test hunk they followed; install::linux is public upstream, so its newly public items are documented; craft-update's oci_migration gates no dependency, so the facade forwards it (design-lint features/gate).
storytold main 83cb1133dd (291 commits) into the integration head bab1a99b85; 47 conflicted files.
- Domain test files (metafile, prepress, pdf plates, settings store, heif, media-testkit, atomic): tests next cut stay cut; tests new on main are kept, as trials where the crate's test target runs trials.
- atomic: main's group-bits test and Faulty::set_group go to src/tests.rs. audio: main's GSM and SBC oracles join tests/main.rs. cms constructors, pdf knockout_backdrop and testing_pdf join their crates' one test binary; timeline's preflight tests become src/preflight_tests.rs trials.
- update: main's changes to detect, install (linux, macos) and the tests land in next's split modules. The app's own offer is inspected on a thread of its own, picked up by tick's polling; settle_for_tests settles offers too. Later on a ready update drops the close it asked for. updater_pin_tests.rs stays deleted; its new pin test is in tests/it/update.rs.
- craft-color: main added a different crate at crates/color (the colour tags of compositor and display frames); it is next's craft-color module `tags`, re-exported at the root.
- Old crates/ui (combo, docking, testing, README) and keymap's ui/view.rs stay deleted; main's new crates/ui/src/testing files are dropped with them.
- New crates in the craft facade: ai, control, dds, frame, ipc, media-source, palette, press-print, score, ssip. testkit and xtask are listed outside it.
- Cargo.lock: the union of both locks, resolved by cargo metadata. Workflow: main's nextest Windows leg, with next's --keep-going clippy.
egui gives the press to an interactable Area's own widget wherever no widget on the layer is.
The overlay host records that widget, and find_under and foreign_target read it as no target,
so the layer's shapes take the press and hover there (a menu's scroll strips).
The roots that contain the pointer are found whatever egui's click target is.
A widget a component made for its own text (a field's text, a selection part)
is recorded with its component: a press egui gives it stays the widget's, and
the hover goes to that component's topmost shape. Collection rows report
pointer_over beside hovered, and the document tab strip names the tab under
the pointer by it, so a drop target reads it while another root holds the
press. DIAG (CRAFT_DIAG_PRESS) prints each resolution's stack and answer.
A new or cropped document's fit and a new arrangement's fits place the view, which jumps as PhotoCraft's
placements did; a menu row or an action step eases under Animated Zoom as its chord does. The full-window wheel
trial turns Overscroll on: after the 20-point fit one notch leaves the image smaller than the canvas, which
Overscroll off centres.