Bump craft-ui to craft-libs 1b34eba and add craft-keymap, craft-dialogs,
craft-quit, craft-menu (macOS) and craft-window.
File dialogs no longer block the event loop. Shortcuts dispatch through
craft-keymap and match exactly their modifiers. On macOS, Quit asks about
unsaved work and the app quits through the platform. On a Wayland desktop
that leaves the frame to the app, the menu bar is the title bar.
Add Help > Check for updates... (ui.help.checkForUpdates), a check at
startup, the update prompt and result dialog from craft-update, and the
Windows update helper entry point.
A copy of the app downloaded directly was never told about a new version.
Runs driven by --control or MATERIALCRAFT_NO_PREFS skip the startup check.
Shortcuts wait while the prompt or a modal result dialog is open. The
update code builds on desktop only; the web build is unchanged.
A moving frame was one ray per pixel at half size, so edges showed as visible
stair-steps until the full-quality frame landed. It now uses 2x2 rays and picks the
largest of four levels (half size 1 ray, half size 2x2, three-quarter 2x2, full 2x2)
whose last frame took under 32 ms, dropping a level when a frame goes over. The lowest
level is the previous frame, so a slow machine does no worse than before.
* ci: reduce integration test executables and skip unused tool install
* test: retain process isolation for language switching
---------
Co-authored-by: FredApps <FredApps@users.noreply.github.com>
Loading a mesh should fail with a package error instead of allocating unbounded vertex buffers first, matching the existing triangle limit intent.
Add a vertex-count bound checked while parsing OBJ and glTF positions so excess vertices are rejected before the full mesh is collected, with a regression test using an OBJ whose vertex count exceeds the bound but whose triangle count does not.
Test: obj_with_excess_vertices_is_rejected failed before the change and passes after.
The properties panel's "Expose as graph input" sent the bare parameter
id as the new input's id, so exposing Opacity on a second Blend node
failed with "an input is already called `opacity`". graph.exposed.add
now accepts a bound input without an id and names it after the
parameter, kept unique (opacity, opacity_1, ...), and the menu relies on
that. An explicit id must still be free.
The W3C color-dodge formula keeps a black background black even under a
white foreground, and color-burn keeps a white background white even
under a black foreground. blend_channel checked the foreground first, so
both edge cases came out inverted.
Fixes#135
The main parameter slider already snaps to round values, but the toolbar slider does not, so the same drag cannot land on exact values there.
Apply the same aim-radius smart_aim calculation used by slider to bar_slider, and add a drag test through the existing slider harness that aims near a round value on a bar slider.
Test: bar_slider_drag_reaches_exact_round_values failed before the change and passes after.
A dot is 14 units wide with a port on each edge, and each port's 9 px
hit circle covered the whole dot, so pressing it started a wire (or did
nothing) instead of moving it unless the view was zoomed in. The dot's
body now wins over its ports, and its grab area keeps a 16 px minimum
on screen. Wires still start from just outside the dot.
Fixes#100
A panicking cook or control command should become an error reply and toast, not crash the app and lose unsaved work.
Make guard report a non-empty unknown-panic message for non-string payloads, and wrap control dispatch and session.inspect cooking with guard so panics are caught in the worker, app, and control paths.
Test: guard_reports_unknown_panic_payload_instead_of_empty failed before the change and passes after.
Data maps read as sRGB get the wrong values when a material is exported, shifting normals and scalar maps.
Choose the decode color space from the input node's usage (linear for non-sRGB usages, sRGB otherwise) when reading input bitmaps in export_material, with a regression test using a mid-gray data input.
Test: export_material_decodes_data_inputs_as_linear failed before the change and passes after.
An export that collides with a file already in the destination currently overwrites it without warning, losing the existing file. Rejecting the collision before writing protects existing files and makes the failure explicit.
Check every target path in the destination directory before creating or writing any output, and return a file.export error naming the colliding filename if one already exists. Add a regression test that places a sentinel file at an output name, runs file.export with unique identifiers, and asserts the export fails and the sentinel is unchanged.
Test: export_rejects_existing_file_in_destination_before_writing failed before the change and passes after.
Callers setting a displacement depth expect the height relief to change, but today it is silently ignored unless the HQ flag is also set.
Use the requested displacement depth whenever it is provided, falling back to the view height_scale only when it is absent, and add a regression test rendering with and without displacement and without hq.
Test: render_displacement_applies_without_hq failed before the change and passes after.