With automation read roots in force, an SVG or SVGZ that would name a
linked image's file outside them is refused before any file, folder or
reply is written, with "a linked image file is outside the read roots",
which names no file or folder. An <image> names the file with
images: link, and with embed when the document holds no pixels for the
image. With preserveEditing, the native document the SVG carries names
every linked image and placed file, the relative paths kept of them and
each data set's image, so those are checked too, and a stored brush
entry that does not read as a brush is refused because its links cannot
be checked.
- The check runs where the linked JavaScript check runs:
document.serialize, document.export, document.exportSelection,
document.exportForScreens and assets.export, every SVG and SVGZ save,
file.exportAs and the SVG Options dialog's Show Code. It also covers
clipboard.exportSvg, and a Copy that an automation request asks for
puts no SVG on the system clipboard when it would name such a file.
- Only the art each file writes is checked: the selected objects with
selectedOnly and Export Selection, the art over each chosen artboard,
hidden layers and objects only when hiddenLayers is on (a save keeps
them by default), never template layers or the symbol or opacity-mask
editing layer, and the symbols, patterns and brushes that art uses.
An image colorized with a solid fill whose pixels are gray or missing
names no file, so it is not checked outside Preserve Editing.
- Embedded pixels, a file inside the roots, a relative path that leads
inside them and a URL are written as before, and the person at the
keyboard exports every link as stored.
Docs: docs/mcp.md, docs/target-app-parity.md and the params text; de
and nl rows for the new message, next to the JavaScript message's rows.
swatch.edit stored a replacement gradient without its placement, so a
radial gradient with an aspect, Alt-dropped on a gradient swatch or
given as `paint`, lost that aspect, while swatch.new keeps it and
applies the swatch with it. A gradient given an aspect without `start`
and `end` lost the aspect in both commands. A replacement pattern kept
the tile transform of the swatch it came from, while swatch.new stores
a pattern untransformed, and `paint: {pattern: name}`, which an Alt-drop
of a pattern fill sends, was refused.
swatch.edit and swatch.new now store a gradient or pattern through one
helper: a gradient keeps its aspect, with or without a vector, and holds
no swatch link, and a pattern is untransformed. swatch.edit takes a
pattern by name, as swatch.new does.
brush.freehand drew the plain path when `brush` named no brush in the
document or was not a string, and drew a pencil stroke for any `style`
other than "brush". It now refuses an unknown name with "no brush named
`<name>`", as brush.apply and brush.setCurrent do, a `brush` that is not
a string, and a `style` other than "pencil" or "brush". The document does
not change and no undo step is recorded. A `brush` left out or null still
draws the plain path.
The Paintbrush skips a tool brush or current brush that has been deleted
and paints with the other, or draws the plain path when neither is in the
document, so a stroke after a brush is deleted is not refused.
With points of a gradient mesh picked (Mesh tool, Direct Selection or the
Lasso), a solid fill color from the Color panel recolors just those points,
but the Fill proxy, the Color panel, the Color Wheel and the Control bar's
fill chip kept showing the mesh object's own fill, so the panel's sliders
jumped back after each drag.
- The new `Session::fill_mesh_points` resolves the targets as
`paint.setFill` does: the picked points of every selected mesh, unless the
Appearance panel's active row is a fill or an object of a symbol instance
is selected. When the first selected object is a mesh among them, the Fill
proxy (`paint.proxies`) shows its first picked point's color, and "?"
compares the picked points' colors with each other and with the other
selected objects' fills.
- `Session::mesh_points_picked` lists the points `transparency.set` fades: it
is empty while the Appearance panel's active row takes the opacity, and
`transparency.info` and the Transparency panel now follow it there too.
- The cached "?" state and the Transparency panel's values are recomputed when
other points are picked, which gives the document no new revision.
- The Control bar's opacity shows the first picked point's opacity, which
`transparency.set` changes then.
- The `paint.setFill` and `transparency.set` params texts name the picked
points instead of the point last clicked, and the `paint.proxies` text,
docs/mcp.md and the progress doc describe what the panels show.