Node search takes no keys, focus or outside clicks while input is
blocked and does not open behind a blocker. The add-node menu's letter
filter does not change while blocked. Sample tiles are disabled behind
a dialog. A file dialog keeps its commands enabled only when nothing
else blocks input. The control protocol notes that the installed-update
notice does not block.
Delete edited the package behind the Save, Discard, Cancel prompt, and
floating OS windows stayed live behind every dialog, because no single
function said whether input was blocked.
Modality::capture answers it from the app's dialogs, the unsaved prompt,
native file dialogs, the update prompt and result window, and egui's
modal layer. Shortcuts, Graph, Function and FX-Map keys, the node search
and add menus, file drops, floating OS windows, Home's actions and menu
items all read it. Home and the Shortcuts list do not block.
Behind a file dialog, the commands that show one still run, so File >
Open brings a hidden macOS Open panel forward.
ui.menu.invoke now returns an error behind a dialog instead of ok,
ui.menu.list reports those items as disabled, and package_save without a
path in bridge mode returns the same error. command.run is unchanged.
Floating panels drawn inside the main window, as on the web build, still
take clicks behind a dialog until the dialogs use egui's modal layer.
Pressing an unconnected input and dragging now pulls a wire out of it,
and dropping it on another node's output connects the two, in the
material graph and in the function graph editor. Dropped anywhere else,
nothing changes. #53 added this to the material graph, but it was lost
when the canvas was rebuilt as the graph/ module.
Fixes#13
* 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>
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.
Replace the legacy Rust procedural library with clean-room native primitives, typed function execution and FX-Map graphs. Save supported content as native SBS and organize the model, evaluators, codecs and editors into focused modules.
Add shared graph editing behavior, flat filtered node menus, frame and comment editing, named Explorer outputs and an original atomic sample. Document the tested scope and remaining interoperability work.
Restore tracked files to 91bb53f07a, immediately before the batch, at the maintainer request. Preserve the existing history and earlier work, including PR #38. Revert the 50 reviewed PR merges and the version bump in 441092c. The published 0.1.2 release is unchanged.
materialcraft-cli mcp and serve now take the --automation-*-root spelling
the other crafting apps use, as aliases of --read-root / --write-root. The
parser stores them under the short names, so the last root given wins
whichever spelling it used. Adds unit tests and a note in the protocol doc.
Fixes#55
Co-Authored-By: Claude Opus <noreply@anthropic.com>
Sandboxed agents could not hand a material to TextureCraft: the workspace
sandbox refuses `file.*` commands and there was no MCP tool for `.mcmat`.
Add `material_export {path, graph?, size?, values?}` (RPC method
`material.export`). It cooks the graph through the same engine code as
`file.exportMaterial` and writes the `.mcmat` only through
AuthorizedWorkspace (cap-std, `--write-root`): no write root, a malformed
path or an escape is an error, the parent folder must exist, and the file is
capped at what `package_open` may read back. Bridge mode refuses it like the
other path tools. The engine gets a shared `material_request` helper so the
command and the tool parse graph/size/values identically.
Tests: file written and readable, bad requests, denied without a write root
(Denied and read-only workspace), path escapes (`..`, absolute, backslash,
drive, symlink) and the MCP tool end to end. docs/control-protocol.md lists
the method and tool.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
- Add full Arabic translation table (363 entries) in crates/ui-egui/src/i18n/ar.rs
- Implement live language switching, locale detection and RTL support in crates/ui-egui/src/i18n.rs
- Add system font fallbacks for Arabic (Segoe UI, SF Arabic, Noto Sans Arabic) in crates/ui-egui/src/fonts.rs
- Add language selector combo box to Preferences dialog in crates/ui-egui/src/windows.rs
- Add language preference persistence in crates/ui-egui/src/state.rs
- Update docs/localization-parity.md tracking Arabic support
The app wrote its control token to the temp folder with default permissions from a
hash-based generator, compared it with ==, spawned unlimited threads and let an
unauthenticated client hold a connection for 10 minutes. The shared token file was opened
with create+truncate, which follows a planted symlink.
- Token files are created new (remove, then O_EXCL) with mode 0600; clients only read a
regular, owner-only, non-symlink file.
- The app's control server uses the shared security module: OS-random token, constant-time
compare, bounded lines, at most 16 connections, one auth attempt within 10 s, close on
malformed JSON before auth.
- serve --port and the app bind before writing the token file.
Ported from TextureCraft 5a065c1 and 836e3f2.
Move the Levels screenshot's ATTRIBUTION row, the README mention, the
architecture note and the snapshot scene to places #36 does not touch, so
the two pull requests merge in either order without conflicts. No change
in behavior; the snapshot scene now runs last.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Selecting a Levels node now shows a visual editor above its sliders: a
histogram of the node's input (256 bins; red, green and blue overlaid for a
color input; scaled to the tallest bin between pure black and white) with
the clipped ranges shaded and the levels transfer curve on top, draggable
input low/mid/high handles under it and output low/high handles under a
black-to-white bar.
Fixes in how Levels is edited: Level in mid is relative to the input range,
and its handle now sits where it acts and moves with the range; the input
low and high handles cannot cross. Parameters bound to inputs or driven by
functions keep their handles locked. Every drag is a graph.node.param
command, one undo step per handle. levels_fn no longer propagates NaN.
Tests cover the histogram, the handle constraints and the remap math; the
snapshots UI test renders the editor. Documented in docs/levels-editor.md.
Clean-room implementation.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Shift+click adds a wire to the selection and Ctrl+click toggles it. With two
or more wires selected, X swaps where they come from: two wires trade
sources, more reverse them in target-node and input order, so selecting a
Blend node's foreground and background wires and pressing X swaps the two
layers. The wires stay selected, so X again swaps back. Delete and
Backspace remove every selected wire in one undo step, and the wire menu
gains Swap selected links and Delete selected links.
New commands graph.wire.swap and graph.wire.delete take
{wires: [{to, toPort}, ...]}; a swap that would make a cycle is refused and
changes nothing. Engine and UI tests (real clicks on a Blend node) cover
both; docs/wires-and-alpha.md documents the gestures, the ordering rule and
the commands.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>