* FreeBSD CI: run the GPU crates' tests one at a time
The FreeBSD VM's software Vulkan driver crashes (SIGSEGV) when several tests create a wgpu device at once. texturecraft-render's lib and headless tests, and earlier texturecraft-automation's, died this way in every FreeBSD run since Nov 6, with no render or dependency change. photocraft already serializes its GPU tests for the same reason; do the same for the crates that open a device.
* FreeBSD CI: test the whole workspace one test at a time
Excluding the GPU crates from the parallel run changed feature unification, and winit then built without its X11/Wayland backends (compile_error on FreeBSD). Run the whole workspace in one cargo test with --test-threads=1 instead.
Applying a material filled the model in tile by tile, and each apply made the
next one slower. Now:
- a big recomposite first draws a coarse look of every tile (sampled texels
repeated across blocks), then refines to the exact result;
- layers hidden behind an opaque layer are skipped (not when anchors or height
masks are involved);
- compositing and upload budgets adapt: larger when idle, smaller while the
user is interacting, and uploads reserve time for conversion;
- no coarse pass during a live stroke or with neighbourhood filters;
- blending at full weight returns the blended value exactly.
Tests: coarse-then-exact, hidden-layer culling gives identical pixels, coarse
pass covers every tile, no coarse pass while a stroke is live.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Merge upstream main into the branch. The streamed bake now returns the same Arc buffers it handed to the preview, and the document stores those, so a preview never holds a second copy of a map. A cancel leaves the set being baked as it was; sets that finished earlier stay applied.
Bumps craft-ui and craft-window to craft-libs 1b34eba4 and replaces the
app's own dialog, shortcut and quit code with the shared crates.
File dialogs go through craft-dialogs and no longer stop the frame. An
action that needs a path asks for it and continues when the dialog
answers. An answer that acts on the project does nothing, with a toast,
when another project was opened meanwhile. The browser build keeps its
pickers and the startup and crash message boxes stay blocking.
Shortcuts run through craft-keymap's dispatcher, in the main window and
in floating panels. Saved shortcuts keep their stored form, and the
Keyboard shortcuts window and the shortcut labels do not change. A
shortcut on a symbol that needs Shift is recorded without Shift, and
saved shortcuts in the old form still run. A shortcut now runs only on
its exact chord: an extra Shift or Alt no longer runs a plain-key
shortcut.
A window close quits through craft-quit, and the close check runs in
logic, so closing a minimized window with unsaved changes restores it and
asks. A close during a stroke finishes the stroke and asks. The macOS app
menu comes from craft-menu. The unsaved-changes prompt goes on once its
Save dialog has saved the project, and stays open after Cancel or a failed
save.
The window frame guard on Windows and the title bar's buttons stay in the
app, since craft-libs has no code for them.
TextureCraft is updated only through the launcher, so a copy downloaded
directly is never told about a new version. The desktop app now checks
GitHub releases at start and from Help > Check for Updates, through
craft-update at craft-libs 1b34eba4. A run with --control skips the check
at start. A ready update installs when the app closes, and it waits for
unsaved changes, a stroke, a bake or a resize. The update prompt and the
modal result window hold the keyboard, so shortcuts do not act on the
project behind them. The web build is unchanged.
A project file could set mesh_path to any host file, and automation allows a
file.reimportMesh without a path, so that command would have read it without
workspace authorization. A command without a path now always uses the
project's own copy again. The desktop UI passes the remembered path itself
(Session::remembered_mesh_path, one rule for "remembered and still there"),
and asks for a file when there is none. Also moves the misplaced doc comment
on read_mesh and documents the touched functions.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Reimport mesh re-read the project's own stored copy of the mesh when it had
one, so saving a change to the mesh file and reimporting did nothing. The
project now remembers the path the mesh was imported from (mesh_path, the
spec's "3D mesh path") and Reimport reads that file again. When the file is
gone the menu asks for one, and a command without a path still falls back to
the stored copy. Projects saved before this have no path and ask once.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Share visualization settings between scene shading and GPU sync, and use then_some for the conditional low-poly pass. Cover per-set distances, selected-set filtering, missing inputs and ownership with engine tests.
Properties gets tolerance, a Colors list (swatch, R/G/B, re-pick, remove)
and a Pick color mode: the pointer becomes an eyedropper, both views show
the ID mesh map and the next click adds the ID color under it.
effect.set takes colors; effect.colorSelection.pick samples the texel the
mask evaluates and skips hidden texture sets.