- A Learn link that locates a tool on a toolbar made with New Toolbar
brings that toolbar to the front once before its button is marked, so
another floating toolbar no longer covers the mark. A group torn off
into a strip still brings the strip to the front instead.
- A docked flyout whose rows are taller than the window scrolls them, and
a Learn link scrolls the located row into view before marking it. The
mark is clipped to the rows' view.
Color and Grayscale traces smoothed a gray photo before choosing its
colors, but a tinted photo with the same tones skipped smoothing: the
0.065 error rule applied only to pictures whose channels stay within 8
levels of each other. A picture whose opaque pixels lie, 19 in 20, within
6 levels of one tone curve now takes the same rule. The curve runs
through the median color of each 8-level stretch along the colors' main
direction, and a pixel on it must also lie within 6 levels of the plane
the colors spread along most, so art in several unrelated colors is not
counted. The sixteen-versus-eight exception still keeps clean flat art
on the flat-art route.
a_shadow_on_each_fill_a_painted_effect_returns_follows_the_transform_after_it
installed test.engine.twofills, which
a_second_painted_effect_on_a_fill_keeps_the_piece_s_other_fills also
installs with a different module. Installed plug-ins are kept for the
whole test process, so running the two tests in parallel could run one
test's effect with the other's module. The test now installs
test.engine.shadowedfills.
Single Word Justification adds no space inside an inseparable pair. A
right-to-left line draws the second half's cluster before the first half,
with the cluster's glyphs in logical order, so a dash followed by a
combining mark puts the mark next to the first dash. The pair is now found
from the two neighboring clusters instead of neighboring glyph indices.
Effects apply in the order they are listed, so an effect listed after a
Transform effect applies to the art the Transform effect made, at its
own values, as an object's later effects do after the object's
Transform effect. With Scale Strokes & Effects on, a fill's or stroke's
own Transform effect scaled the effects listed after it in that fill's
or stroke's list by the mean scale: a 300% Transform turned a 5 pt
Offset Path after it into a 15 pt one, and a Drop Shadow after it took
three times its offset. With Transform Patterns or Scale Strokes &
Effects on, an SVG filter after it also had the origin of its user space
moved.
- The effects after such a Transform effect now keep their values, on
the transformed art and on each copy, on every fill and stroke a
live-effect plug-in paints the piece with, and when the copies are
counted against the effect budget.
- With Transform Objects off, the effects before it keep their values
too.
- The Transform params text, docs/target-app-parity.md and docs/gaps.md
describe the rule, and drop the note that listed an object's later
effects keeping their distances as a shortfall.
With logoColors named, Flat Logo measured how flat the image is against
the named colors. A solid pixel counts as flat only within 22 (RGB
distance) of one of those colors or white. Flat art whose named colors
were 20 levels off in every channel was refused as not flat, and the
refusal score of a gradient changed with the names.
The check now uses the image's own colors, found the same way as when
no colors are named. It looks for as many colors as are named, with
white, or as the Colors setting gives, whichever is more. How far the named colors are
from the image's colors no longer changes whether the image is refused.
This changes one existing behavior: an image with large areas of a
color that was not named used to be refused, and it is now traced in
the named colors.
Docs: docs/image-trace-adjustments.md, docs/target-app-parity.md, the
imageTrace.make params text.
A process color can't colorize a grayscale image that has an alpha channel,
and paint.setFill refuses that combination. Remove Background gave such an
image an alpha channel and kept its process colorize color. It now refuses
the run, changing nothing, when an image it is given is gray and colorized
with a process color. It checks this before any image is decoded. Another
image in the document that already has that combination does not affect a
run on other images. Black, white and spot colors still colorize the result.
The rule check_colorized applies to each image is now one function,
paint::gray_colorized_with_process, which both checks call.
Docs: docs/mcp.md (Remove Background), docs/target-app-parity.md.
tree() in crates/engine/src/cmd/findfiles/tests.rs returns a Tree guard
that holds the canonical path and removes the folder with everything in
it when it is dropped, also when the test panics. When the removal
fails, the guard gives the owner read, write and search permission on
every folder in the tree (Unix; links are not followed) and removes it
again, so a test that panics while a folder is locked leaves nothing
behind. A removal that still fails is ignored.
tree() empties the folder temp_dir returns in place instead of removing
and remaking it, so on Unix the folder keeps the owner-only mode that
temp_dir sets.
The canvas cache key held the process-wide placed-document bitmap
generation, so a bitmap made for a file that only another document holds
changed every document's key, and the next frame differed from the
frame shown in more than the view. In the web build, which has no render
worker, a heavy canvas then rendered in the middle of a pan instead of
waiting until the view was still. On desktop the pan dropped its
low-resolution fill, and the render worker did not copy pixels from its
last frame.
Each document now keeps its own value, checked once per generation
change, as the plug-in key is. The value moves to the current generation
when the document shows a placed document of a file whose bitmap was
made. A file kept only for Undo does not count. When more bitmaps were
made since the last check than are recorded, the value moves when the
document shows a placed document of one of its images. After the
value moves, the part of the frame to draw again comes from the bitmaps
made since the last check before the move, so bitmaps made earlier for
other documents no longer make the whole frame render.
The canvas tests that retried or tolerated a new frame when another test
made a bitmap now assert without those workarounds.
jmverges