The Print dialog's Output section has an Overprint Black checkbox under
Convert All Spot Colors to Process, off by default and available with
Separations (print.setup output.overprintBlack, kept with the document
and in print presets). With it on, solid 100% process K or 100% gray
fills, strokes and characters, and gradients whose every stop (or every
freeform point) is, overprint in the printed copy, so the inks under them
stay on the other plates. Rich, RGB, Lab, spot-linked and lighter blacks
knock out. The document and its own overprint settings do not change, and
composite output ignores the option.
Plates draw an overprinting paint that puts no ink on them as nothing, so
PostScript separations keep the inks below it too. Overprinting character
fills and strokes now darken on PDF plates like fills and strokes, a type
object's own fill in a PDF is drawn with its blending mode, and Edit >
Edit Colors > Overprint Black counts a gradient with a spot-linked stop as
a spot black and a freeform gradient by its color points.
With variation cells selected, the Save Color Group to Swatches button
now saves those cells as one swatch group, in grid order (row by row,
left to right, each cell once), named after the harmony rule, in one
undo step, each color in its own model. With no cell selected it saves
the harmony colors as before.
A cell selection now ends when the guide it was made in changes: the
base, the Color Guide Options, the variation mode, the harmony rule, the
library limit, or the colors the grid shows. Before, changing the
variation mode or the options kept the old cell positions selected, so
Save Colors as Swatches could save colors that were never picked.
With a gray between black and white, an edge pixel of black on white
took the black-and-white blend only when one of its eight neighbors lay
past the gray on each side and the flat black and white areas lay nearer
than the flat gray. On an edge blurred by a pixel or more neither holds,
so gray slivers lined black shapes: a black disc beside a gray square on
white traced up to 35 gray paths at blurs of 1 to 3 pixels.
The check now walks from the pixel along the line between the two outer
colors, up to 5 steps each way, each step to the neighbor that lies
farthest toward one of them while the pixels keep getting darker (or
lighter). The blend of the outer two lies as near as the farther of
their flat areas, or as the larger of the two step counts to a pixel of
each outer color when that is smaller. The first step is the old
neighbor check. The same disc and square now trace with one gray path
at blurs of 1 to 2 pixels. At 3 pixels, with the colors named, a gray of
128 is one path, a gray of 200 leaves 4 slivers with no area, and a gray
of 230 leaves 8 slivers of up to 21 pixels (14 gray paths before).
On edges blurred by a pixel or more, gray near black loses pixels. A
soft-edged gray band up to 4 pixels wide along black traces as black
and white at blurs of 1.5 and 2 pixels, and one up to 3 pixels wide at
blurs of 1 and 3 pixels. A soft-edged gray stroke 2 pixels from black
can lose some or all of its gray, and one 4 pixels away a few pixels. A
soft-edged gray stroke running out of black, blurred by 1 or 1.5
pixels, loses 3 or 4 of the 16 pixels nearest black. Sharp-edged bands
and strokes keep their gray.
Docs: docs/image-trace-adjustments.md, docs/target-app-parity.md.
A click on the isolation bar's empty space, or on the isolated object's
name at the end of the breadcrumbs, leaves isolation mode altogether, as
Exit Isolation Mode does, nested isolation included. The back arrow, the
breadcrumbs of the levels above and the pattern buttons keep their own
actions, and a drag across the bar does not exit.
While an opacity mask is edited the click stops editing the mask. In
symbol editing mode it leaves the mode, also from a group isolated inside
the symbol's art and together with the isolation the mode was entered
from. While a pattern is edited it does nothing; Save a Copy, Done and
Cancel end pattern editing.
Docs: docs/target-app-parity.md.
With `pdfs: "single"` and several assets, layers or selected objects
(`selection: "each"`), document.exportForScreens wrote one PDF named
after the document holding only the first item's art, and every other
item's PDF was left out. Single file puts artboards on the pages of one
PDF; each asset, layer or object is cut out of the document with its own
art, so the export now refuses that combination before it writes any
file, and the Example line refuses it too. `pdfs: "multiple"` still
writes a PDF of each item, and `selection: "one"` writes one PDF either
way.
Docs: params text, docs/mcp.md, docs/target-app-parity.md.
Dropping a layer, group or object's target circle on the Layers panel's
Delete Selection button now runs Reduce to Basic Appearance on that item
instead of Clear Appearance. The item keeps its topmost visible fill and
stroke, loses its other rows and its effects, and is not deleted. A drop
that changes nothing records no undo step. The help page describes this
drag as the alternative to Reduce To Basic Appearance:
https://helpx.adobe.com/illustrator/using/appearance-attributes.html
Before this change the drop also removed the remaining fill and stroke
and reset the object's opacity and blend mode.
In a CMYK document the Fill Color and Stroke Color tolerances run from 0
to 100 and measure the Euclidean distance between the C, M, Y and K
percentages; RGB, Gray and Lab colors are converted to CMYK. RGB
documents keep the 0 to 255 RGB distance. The panel's fields take the
range of the active document.
A tolerance above 100 set in an RGB document is kept and applies as 100
while a CMYK document is active. magicWand.set now returns an error for
a tolerance that is out of range or not a number, and for a switch that
is not true or false, and then changes no setting, reset included;
before, it clamped the values and applied reset first.
A style whose rows paint nothing showed as a blank white tile. Its
thumbnail now shows the preview square or type outlined in black and
filled with white, with the style's effects, under a red slash. The
panel's views, the Control bar's Style picker and chip, the dragged
chip, graphic style library panels and the large preview on the
selected object all show it. A row that paints None does not count as a
fill or stroke; a hidden row or one with zero opacity does.
Holding Backtick while dragging out a rectangle, rounded rectangle,
ellipse, polygon, star or line leaves a copy of the shape being drawn
each time the pointer has moved 8 screen points with the key down, up to
128 copies a drag. Each copy is its own object, drawn as the drag showed
it then. The release keeps the copies and the last shape as one undo
step, and Escape takes them all back. The spacing and the limit are
VectorCraft's own values.
The `backquote` descriptions of `pointer_gesture` name the shape tools.
Docs: docs/mcp.md, docs/target-app-parity.md.
FontLikeness::distance left out every number either face does not give,
so a family whose faces give none of them (static faces with no OS/2 or
post table) was 0 from every family, and Show Similar Fonts could list
it right after the chosen family, as an exact match. Faces that share
no number to compare are now f32::INFINITY apart, so such a family
comes after every family of its script group that shares one, and
families equally far keep their order. The order of measured families
does not change. This is VectorCraft's own rule.
Builds on #7983, which added Show Similar Fonts.
readhexstring and readline called the one-byte file read for every input
character, copying each byte into a new vector. They now scan the bytes
left in the file in one slice and advance the file by the bytes they used.
The results are unchanged: the same bytes, the same boolean, the same next
unread byte, from the program's own file (after the whitespace that ends
the last token), a decoded buffer and a filter decoded when first read.
readhexstring stops on the digit that completes the last byte and drops a
lone digit at the end of the data; readline takes CR LF as one line ending,
leaves the byte after a lone CR unread, and leaves the line ending unread
when the line fills the string.
Tests run the new readers next to copies of the byte-at-a-time loops over
13 stream forms and several hundred inputs, comparing the result and
everything left to read; an image read through a readhexstring procedure
is compared with the same samples given as a hexadecimal string. The
import fuzz tests gain readline and a case for both operators.
data_op allows clippy::cognitive_complexity. Without the allow, clippy
rates it 54 against the limit of 30; with the old loops in place it
passes.
When the colors of an image lie on one line, as a pale gray ground, a
gray panel and a charcoal disc do, an edge pixel between the panel and
the disc is also reproduced by a mix of the ground and the disc. Flat
Logo switches such a pixel to the mix of the classes beside it only when
its neighbors lie on both sides of the class it drops, which a class
beyond both classes of the edge never satisfies. A charcoal disc on a
gray panel on a paler ground traced with 28 slivers of the ground, of at
most two pixels each, around it when its edges were sharp, and with one
sliver when they were blurred by 0.7 pixel, with the colors found or
named.
A pixel now also takes the mix of the classes beside it when the class
it drops lies beyond both of them on their line, the pixel's own
neighbors lie on each side of it, no neighbor lies past the nearer of
the two toward the dropped class, and a chain of neighbors, each nearer
that class than the one before, leads from the pixel, in at most 6
steps, to that class's color or to a flat area of that class. A class
named some levels off the color of its flat areas still counts. The pixels of a pale line on the disc, whether one pixel wide,
blurred over three pixels or falling between two pixels, and the edge of
a gap of the ground's color between the disc and the panel keep the
ground in their mixes. An edge blurred by a pixel or more can still
leave slivers of the ground.
Docs: docs/image-trace-adjustments.md, docs/target-app-parity.md.
Type is drawn as its outlines, so each copy that a fill's or stroke's own
Transform effect makes of type carries the raster effects listed before
it, as a path's copies do. A test checks this for the fill's first
Transform effect and for one listed after a Transform effect with
Transform Patterns on, drawn, expanded and baked.
The progress doc now lists type as covered, states when a later copying
Transform effect does not carry the raster effects before it, drops the
fill or stroke case from the older entry's limitation, and puts the
Rasterize entry back on its own line.
Main now stores a line's or label's added rows by kind (Keep::Kinds),
rewritten paint and row attributes (capture_line_row_writes) and no-op
reorders the way this branch did, so its versions are kept. The branch
adds on top: a stroke painted on a line after its kind lost its stroke
keeps that line's weight, a pasted graph's axis and ring line rows follow
a renamed swatch, and the paint.swap params text says only what the swap
changes is stored.
A clipping object written as art cut to it (a group, an image, a symbol
instance, a live object, type, or a path inside art already cut to
another clipping object) lost its name, opacity mask and variable
bindings in the editing data: no written object carried its dictionary,
and a painted one put its name on each of its fill and stroke objects.
The unpainted path that carried its text wrap options now carries its
whole dictionary, in the form the .ai reader reads (art_dictionary in
crates/eps/src/import/ai/read/document.rs). Its fills and strokes keep
only the opacity mask they are drawn through. The path is admitted by
the object count, so at the object limit its dictionary is never left
on the object before it, and a path whose dictionary comes out empty is
taken out again.