Swatches: a library pattern keeps a global color whose name the document uses

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.
This commit is contained in:
dotCooCoo
2026-11-17 06:20:11 -08:00
parent 485a1e5ae8
commit 9ef93eb563
5 changed files with 49 additions and 4 deletions
+3 -1
View File
@@ -4931,7 +4931,9 @@ them as process colors; `.acb` files are read, never written. A file in the user
same extension and bytes as one there, loads as that User Defined library (category `user`).
From a document, such as a `.ai` or `.eps` swatch library, it reads the colors, tints, gradients and pattern swatches
in the document's order and color groups; `swatch.library.add` brings a pattern swatch's pattern, with its tile and
art, into the document as a pattern swatch under the library swatch's name and in its color group. A document with
art, into the document as a pattern swatch under the library swatch's name and in its color group. A global or spot
color the pattern's art links to keeps the library's color: when the document gives its name another color, it comes
in under a numbered name ("Ink 2") and the pattern links to that. A document with
no swatches, and a `.ai`, `.eps` or PostScript file whose swatches are only the default ones, are refused with
"`<file>` has no swatches of its own". The Swatch Libraries filter of Other Library… lists `.ai`, `.ait` and `.eps`
(`.epsf`) files as well as the library files.