With Interpolate Control Points on, a retracted handle was mapped like
any other and could land a rounding error away from its anchor. On a
smooth anchor, lining the handles up then read that error as a
direction and turned the other handle. A retracted handle now goes to
its anchor's new place exactly.
object.setBounds and guide.move move direct-selected anchors through the
same path as object.move, so they already followed the Interpolate
Control Points preference. They now list `interpolate` in their params
text and reject a value that is not true or false, also when the change
only scales the anchors or only guides are selected. A test covers both
commands with the preference on and off and with the param.
When Add to Swatches brought a library pattern whose art links to a global
or spot color, and the document had that name for another color, the
pattern was relinked to the document's color. Adding the library's color
then made a numbered copy that the pattern did not use. The color now comes
in under a numbered name and the pattern links to it, as an added color
does, and the check for a pattern already in the document compares it the
same way.
Type on a path sits at fractions of its path's length. Scaling the path
non-uniformly changes where a fraction lands (CodeRabbit's case: M0 0 L100 0
L100 100 under diag(2, 1) moves the start bracket from (200, 0) to (150, 0)).
Path type now bakes the vertical scale into the character sizes and scales
its path uniformly by it, which keeps every fraction where it was; the
horizontal stretch stays in the transform.
Baking an object's scale into the character attributes removed that scale
from the type's transform, but the area frame (and a path type's path), which
is drawn through that transform too, kept its unscaled size. A 120 x 80 frame
scaled 200% shrank back to 120 x 80 on the page, so the 24 pt type broke into
two lines and the rest became overset.
The frame and the path now take the scale the transform loses, so they, the
line breaks and every glyph stay where they were.
Fixes#8297
When one Add to Swatches call added a pattern swatch and then a global or
spot color its art links to, the pattern brought the color in and the color
was added a second time as a numbered copy. The color the pattern brought
now takes the library swatch's place and color group instead.
With Transparency off, Optimize to File Size's Auto Select counts the
colors of the pixels blended over the matte, which are the colors the
file is written with, so art whose blended pixels need more than 256
colors starts with JPEG instead of GIF.
Adding a library pattern swatch reused a document pattern with the same
tile options and art even when that art paints with a pattern of the same
name and a different definition, so the library's inner pattern never came
in. A pattern whose art uses other resources is now matched by importing it
into a copy of the document, which compares those resources too.
The reader also counts pattern brushes, a pen's included, whose bitmap
it could not read, so the warning now says "image or pattern brush".
The document.open and clipboard.importEmf params text, docs/mcp.md and
the crate doc list the new warnings. A WMF test covers an unreadable
pattern brush and a DSTINVERT bit block transfer.