Visit at most four output tiles per closing work unit and honor the caller's deadline between batches. Sparse images with distant opaque corners otherwise make one final poll scan the whole resized surface.
Add a sparse-output regression at 8, 16 and 32-bit requiring multiple closing polls, identical pixels, and removal of the same empty tiles. Formatting and whitespace checks passed; compilation and test execution await hosted CI.
Each language PR set the array length for main plus its own entry; with six new
languages merged together the registry has 34 entries.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
After the Move tool (or a ⌘-drag) moved the selected pixels, they stayed
floating, and a plain Marquee or Lasso drag on them moved the pixels again.
Photoshop moves only the selection outline there.
A plain selection-tool press on a floating piece is now an outline drag:
the press drops the piece where it is (Move), then the drag moves the
outline (Move Selection). ⌘ and ⌘⌥ drags still move or copy the piece,
and the cursor over the piece follows suit (move cursor plain, arrow
with ⌘).
Fixes#11368
* PSD write recipes: keep every exported candidate and pin the base file
A case that failed after export dropped out of manifest.json, losing the
file a reference-editor check most needs. The CLI also reopened the corpus
path after the hash was taken.
- Keep the candidate and its hash once export succeeds.
- Run the CLI on a copy of the hashed bytes, so it never opens the corpus.
- Compare numbers by value, so 17 equals 17.0.
- tracking-split also checks runs 0 and 2 and all three run lengths.
Part of #6130.
* PSD write recipes: compare large integers exactly, reject case-only id clashes
Converting to f64 made 9007199254740993 equal 9007199254740992. Ids that
differ only by letter case name one output directory on a case-insensitive
filesystem, so they are now rejected as duplicates.
* PSD write recipes: test that the CLI receives the hashed bytes
* PSD write recipes: reject the contour library commands
Their path param can read or write any file, including the pinned base and
the corpus, and they edit no document.
With the Background among the selected layers, a press on a Move-tool
transform handle showed the locked-layer alert but was still forwarded
to the Move tool as Down (and, for a click, the tap and Up), so
Auto-Select could change the layer selection. begin_transform_controls_at
now returns ControlsPress (Missed / Started / Refused); the canvas press
and click paths and the ui.pointer path drop a Refused press. Tests drive
real canvas frames (click and drag) and ui.pointer, with an unselected
layer under the handle.
Co-Authored-By: NaufalDzz <NaufalDzz@users.noreply.github.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Empty commit so the draft batch PR can be opened before any candidate
PR is reviewed and merged on.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The position-locked branch of the Move pick now records app.move_pick too, through one helper shared with the main pick, so Expand layer group on click governs it.
The marker now carries the frame it was set in (app.frame). The Layers panel's track() accepts it only in that frame or the next (the panel and the canvas can draw in either order within a frame); an older marker, left by a pick while the panel was hidden, is discarded, so a later command change that lands on the same layer expands its groups. Chosen over clearing at the end of every frame because the panel may draw before the canvas and would then never see the marker.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Placing by click with no board selected now sends the tool option's preset along with the explicit rect. layer.new.artboard keeps an explicit rect for the size and stores the preset name, so the bar shows the preset instead of Custom. Drawn boards stay Custom.
The swatch shows a custom background as 8-bit RGB, but the stored Color is f32 with alpha. set_background now skips selected boards whose custom colour already has the picked RGB, so OK without a change adds no history step and keeps alpha and precision bit-exact.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Main gained #10879: a Layers panel filter that hides the selected layer deselects it, as in the
reference application. Three #11238 tests expected "Other" to stay selected under a "link" Name
filter. They now check the combined behaviour: Find Layers selects none of the matches and keeps a
selected layer the filter still lists, and the filter deselects what it hides. Also the module
order rustfmt wants after the merge.
Co-Authored-By: NaufalDzz <NaufalDzz@users.noreply.github.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Two review findings on #11238 (#10884):
- `engine.execute` runs `select.findLayers` through `PhotocraftApp::run`, not `menus::invoke`, so
the Layers panel's Name filter was never set on that path. `run` now applies the reply's filter
after every Find Layers (menu, shortcut, `engine.execute`, action steps).
- A blank or whitespace `name` replied `selected: []`, while the panel doesn't filter by a blank
Name and lists every layer. It now lists every layer.
Co-Authored-By: NaufalDzz <NaufalDzz@users.noreply.github.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A stuck close no longer holds up the files queued behind it (up to four
closer threads), and a query identifies the current file by the configured
folder. Tests don't read the room and the status across a late answer, and
the growth-check step proves its query is stalled.
Two CodeRabbit findings on #11249:
- A layer.newFillLayer.gradient step with from, to and stops plays the
stops, but the ATN export refused it. from/to are now left out beside
stops.
- A recorded Make whose Usng also held a name, opacity, mode or clipping
loaded as the plain command, which plays none of them and saved back
without them. It now stays the recorded step.
Each has a test that fails without the fix.
Co-Authored-By: NaufalDzz <90562913+NaufalDzz@users.noreply.github.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
With boards selected the swatch and dropdown show the first board's background, and a choice sets every selected board in one layer.artboard.set step (Edit Artboard / Edit Artboards) and the tool option. layer.artboard.set takes a layers array for this. Also drops the bar_size dead_code allow and adds the placed-board size test.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Add New Artboard's click now uses bar::bar_size (the selected board's size, else the tool option W/H the bar shows) instead of its own fallback to the document size.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
layer_reveal gated on the current tool, so a Ctrl-click temporary-Move pick from the Brush still opened the group. The Move-way pick in tool_input.rs now sets app.move_pick to the layer it made active; layer_reveal::track consumes it and applies the option only to that pick. Every other active-layer change keeps revealing.
Auto-Select XOR Ctrl decides whether a click picks, so the Ctrl-click tests turn Auto-Select off first.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
The flyout row discarded the result of edit.toolbar, so a rejected command (for example by an automation policy) just closed the flyout silently. It now sets the status bar error like other panels.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
The whole folder change now waits 2 s at most, old files close on one
background thread, the cap counts query threads until they finish, and
writes during a query aren't counted twice. Capacity is refused if a sweep
paused spilling meanwhile, a query opens a file unless this folder has one,
and on macOS an unrelated dead mount only costs the purgeable figure.
Main's #11383 renamed an arrow-key run's History step to "Nudge", as the reference
application names it; #10438's new zoomed-out test still expected "Move".
Co-Authored-By: hectorviov <hectorviov@users.noreply.github.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Review fix-ups on #11249 after merging main:
- A midpoint outside 5..95 %, transparency stops out of range or out of
order, and a Gradient Fill Set without transparency stops stay
reference-application steps instead of playing clamped or keeping the
layer's own transparency.
- An inverted Blend If range stays a reference-application step; the
command rejects it at play.
- The Layer Style dialog's OK records `Lefx` = {Scl} beside Blend If on a
layer without effects (measured). That Set is still the dialog's one
step and saves back with the `Lefx` it was recorded with.
Co-Authored-By: NaufalDzz <90562913+NaufalDzz@users.noreply.github.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>