The tangent of 180 degrees in radians is about 1e-16, not 0, so a shear
by 180 or -180 moved coordinates very slightly and recorded an undo
step. Angles within 1e-9 degrees of 0, 180 or -180 now shear by 0:
without `copy`, nothing moves and no undo step is recorded.
Docs: params text, docs/mcp.md.
The Shear field stopped at -89 and dropped any value of 90 or more without a word.
It now sends every typed, stepped or picked value to `object.shear`, which shears by
the tangent of an angle from -359 to 359. For ±90, ±270 and an angle outside that
range the status bar shows the command's error; the art is unchanged and no undo step
is recorded.
object.shear clamped its angle to -89..89 without an error, so any angle
past 89 sheared by 89. It now takes the Shear dialog's documented range
of -359 to 359 degrees and shears by the angle's tangent, so 120 slants
as -60. An angle outside that range, and +-90 and +-270 (within 1e-9
degrees), where the tangent is unbounded, return an error naming
`angle`; nothing moves and no undo step is recorded.
Docs: params text, docs/mcp.md, docs/target-app-parity.md.
A damaged .ai can give a gradient mesh whose outline is enormous but finite.
draw_mesh_raster flattened that whole outline in device pixels (grown_outline),
and kurbo's flatten then asked for more segments than memory holds: a
"capacity overflow" panic (seen in import_fuzz's ai_written_meshes_never_panic).
An outline wider or taller than 2^24 device pixels now goes to the per-quad
drawing path the function already falls back to.
A third quick click on a swatch counts as a triple click, and so does
each quick click after it. Those clicks still applied the swatch, so a
triple click on a pattern swatch opened pattern editing and then
painted the tile art with the pattern itself. Only the first click of
a run of quick clicks now applies and selects the swatch.
The test now sends four quick clicks and gives the art a solid fill in
each view, so the list view's first click is checked on its own.
Running a script or a plug-in now ends the spot color base's link, as a
batch step already did, so a script that deletes the spot color and makes
another of the same name does not make the new one the base. Commands that
only list scripts or plug-ins keep the link.
While the link waits for an Undo, the color it captures before a command is
the one the guide shows, not that of a new spot color of the same name.
The second click of a double-click on a swatch also counted as a plain
click. After the double-click opened pattern editing, which selects the
tile art, that click applied the pattern swatch to the tile, so the
pattern held a copy of itself. The second click now only opens the
editor; the first click still applies and selects the swatch.
Reported by erolkarino. #7164 by mockydevs makes the engine refuse
painting the tile with its own pattern; this change stops the swatch
panel from sending that paint on a double-click.
The Enclosing Lasso Tool joins the Lasso group in both shipped
toolbars, right after the Lasso, and stays in Object › Plug-ins ›
Enclosing Lasso. The All Tools drawer lists it once, under Select, and
Edit › Keyboard Shortcuts › Tools lists it once. It has no default
shortcut, and the Lasso keeps Q. A toolbar the user already edited
keeps its saved layout; Reset Toolbar adds the tool.
Fixes#6117