Commit Graph
223 Commits
Author SHA1 Message Date
dotCooCoo 6d4af2cb6a Merge main into feat/object-mosaic-dialog 2026-11-18 06:12:45 -08:00
BFlat 50c7208fe3 Merge pull request #8466 from dotCooCoo/perf/find-command-index
Commands: find_command looks commands up in an index built once
2026-11-18 13:15:20 +07:00
BFlat 8c80810f2a Merge pull request #8050 from dotCooCoo/feat/interpolate-control-points
Direct Selection: optional preference interpolates curve handles when an anchor moves
2026-11-18 13:12:30 +07:00
BFlat e63768c862 Merge pull request #8425 from dotCooCoo/fix/action-batch-step-numbers
Actions: action.batch errors count steps from 1 and name the member they reject
2026-11-18 13:05:15 +07:00
BFlat 10d3566033 Merge pull request #8499 from dotCooCoo/perf/params-keys-once
Commands: each built-in command's parameter keys are parsed once per process
2026-11-18 13:05:06 +07:00
dotCooCoo c0dce666c9 Merge main into feat/object-mosaic-dialog 2026-11-17 19:59:54 -08:00
dotCooCoo de06497716 Commands: each built-in command's parameter keys are parsed once per process
Session::execute asked about a command's params description several
times per command (the key check, whether `id` stands for `ids`, whether
it takes `ids`), and each question parsed the description again, with a
command lookup for each word after the first of each `…` entry. The
engine now reads every built-in description, and the ones its `…`
entries name, once into a table keyed by the description's address and
length, and answers accepted_keys, takes_key, id_stands_for_ids and
check_keys from it.

A plug-in command's description, and a built-in description whose `…`
entries name a plug-in command, are still parsed where they are used,
since plug-ins change while the app runs. The keys, answers and error
messages are the same; tests::params_cache compares them for every
built-in command against a fresh parse.

In a release build on a one-object document, object.move with ids and
dx takes 48 us of thread CPU time per command instead of 61 us, and
select.set with ids 2.3 us instead of 3.2 us (medians of 7 alternating
runs of 20,000 commands in one process, while other builds were running;
tests::params_cache::bench_params_keys_once). The time is saved per
command, in scripts, batches and MCP or plug-in call loops, and does not
grow with the size of the document.
2026-11-17 17:12:35 -08:00
dotCooCoo f623a28bb0 Commands: find_command looks commands up in an index built once
find_command searched the list of about 1,000 built-in command specs in
order on every call, and a top-level command looks its id up at least
three times before it runs. It now finds a built-in in a map from id to
spec that is made on the first call. When an id is listed twice, the
map keeps the first spec, which is the one the search returned. An id
that is not a built-in still goes to the installed plug-ins' commands
at the time of the call, so installing or removing a plug-in shows at
once and built-ins keep precedence.
2026-11-17 14:27:14 -08:00
dotCooCoo 59fbf8bbe6 Merge main into feat/interpolate-control-points 2026-11-17 12:42:20 -08:00
dotCooCoo 4a60b78b5c Actions: action.batch errors count steps from 1 and name the member they reject
action.batch refused a bad step before any file opened as `commands[i]`,
counted from 0, while a step that failed as it ran was named
`action step N (`id`)`, counted from 1. A step whose params its command
refused gave only the command's own error, without saying which step it
was.

- The checks before the batch (no command, an unknown command, a nested
  batch, prefs.import) now name the step as `action step N (`id`) failed:`,
  from 1, as the runtime errors do. A long unknown id is cut short in the
  message, as an unknown key is.
- The parameter check names the action.batch step whose params it
  refuses the same way. command.batch keeps passing the step's error on
  as it is.
- Override Open matches only document.open, and Override Save only
  document.save and file.saveAs: file.open, file.save and document.close
  are not engine commands, and a step with one is refused as unknown.
  The params text no longer lists them, and docs/mcp.md says a step with
  file.open or file.save is refused as an unknown command.
2026-11-17 12:09:17 -08:00
dotCooCoo 17a8152cd0 Merge main into feat/object-mosaic-dialog 2026-11-17 09:44:16 -08:00
dotCooCoo c4ead8e46f Transform: Rotate Bounding Box… turns the selection's bounding box without moving the art
Object › Transform › Rotate Bounding Box… asks for an angle and turns the
bounding box of the selected objects by it, leaving their art where it
is. Reset Bounding Box squares it again.

- object.rotateBoundingBox {angle, absolute?}: by default the box turns
  by angle from the angle the selected objects share (0 when theirs
  differ); absolute: true turns it to angle. Objects with different
  angles get one shared angle, and the objects inside a group or a
  linked opacity mask turn with it and keep their relative angle. A path
  of a compound path selected on its own turns only its own box, the
  same objects the transforms move. An angle within 1e-6° of 0 is
  stored as 0. One undo step, none when every box is already at the
  angle. A missing or non-numeric angle is an error. changed counts
  every box that turned, as object.resetBoundingBox counts the boxes it
  squares.
- object.resetBoundingBox squares only the box of a compound path's
  path selected on its own, instead of the whole compound path.
- Menu labels in every catalog.

Docs: docs/mcp.md, docs/target-app-parity.md.

Part of #5954.
2026-11-17 08:28:29 -08:00
dotCooCoo 8f0379cc3f Flare: distribute the first ring for small seeds 2026-11-17 05:07:35 -08:00
dotCooCoo 7e769b611c Merge main into feat/circle-through-three-points 2026-11-16 10:43:27 -08:00
dotCooCoo 33defecb66 Merge main into feat/interpolate-control-points 2026-11-16 10:42:29 -08:00
dotCooCoo eeb5bcab7c Merge main into feat/circle-through-three-points 2026-11-16 08:26:14 -08:00
Sven Lafebre 8c53f8ce88 Fix #8093: Pathfinder takes a clip group's members where its mask shows them
Pathfinder collected a clip group's members as if it were a plain group, so
Divide cut the hidden art too and the result lost the mask. Each member is
now cut to the group's clipping region first (nested clip groups by each
region in turn): its area is intersected with the region, and Divide's
cutting lines keep only their parts inside it. A member the mask hides gives
no piece, a group among other objects takes the style of its top member that
shows, and a selection the masks hide altogether is refused with a reason.
This applies to every object.pathfinder.* operation, which also covers Merge
on masked art (#3367).
2026-11-16 12:23:10 +01:00
dotCooCooandbentschener 49a9a0f4cb Direct Selection: optional preference interpolates curve handles when an anchor moves
The new General preference Interpolate Control Points When Moving
Anchors (`interpolateControlPoints`, off by default) is the default of a
new `interpolate` param of path.moveAnchors (a Direct Selection drag),
object.nudge (the arrow keys), object.move, object.transform and
object.transformAgain. With it on, a move of direct-selected anchors
re-maps both handles of each segment with one moved end by the turn,
uniform scale and move that take the segment's old ends to its new
ends, so a segment between two corner anchors keeps its shape relative
to its ends.

- A segment with both ends moved, or with its ends at the same place
  before or after the move, moves as it does with the preference off.
  Only an exact move re-maps handles; any other transform of the anchors
  is applied as before.
- A smooth anchor keeps its handles in line: its re-mapped handle takes
  the new length and stays in line with the other handle, and when both
  of its handles were re-mapped they point along the mean of their
  directions. When the two point the same way, both move with the
  anchor as with the preference off.
- The value used joins the command's journal entry and Transform
  Again's options, so a replay or a repeat re-maps the handles alike
  whatever the preference is then. A non-boolean value is an error.
- A retracted handle stays retracted, each drag or nudge is one undo
  step, and a nudge of 0 still records none. Align and Distribute, and
  the anchors of type paths and area type frames, move as before.

With the preference off, moves give the same result as before. The
label has a row in every catalog. The hook in transform_anchors follows
the patch bentschener attached to #7832; the handle math differs.

Fixes #7832

Docs: docs/mcp.md, docs/target-app-parity.md.

Co-authored-by: bentschener <353895224+bentschener@users.noreply.github.com>
2026-11-15 22:26:18 -08:00
dotCooCoo 7ff63a6cd7 Merge main into feat/line-segment-common-tangent 2026-11-15 18:40:40 -08:00
dotCooCoo 6c3a092996 Line Segment: a line from one curve to another snaps to their common tangent
With Smart Guides and Snap to Tangent on, a Line Segment drag pressed
anywhere on a convex closed path with curves and dragged to within the
snapping tolerance of another such path lands on a common tangent of the
two. Both ends move to where the line touches the paths, the start sliding
along the first path. The line is the tangent whose touch point on the
second path is nearest the pointer, so moving the pointer around that path
switches between the outer tangent and the one crossing between the paths.
Each end shows the "tangent" label when Anchor/Path Labels is on, and the
line is drawn as a guide when Alignment Guides is on.

Before this change the start of a Line Segment drag always stayed where it
was pressed. It still does when Shift, Alt or Space is held, when an
anchor, center or crossing lies nearer the pointer than the second path,
when the press snapped to an anchor, center or crossing off the first path,
when Snap to Tangent is off, when Snap to Grid or pixel snapping places
drawn points, or when either path bends inward somewhere or has more than
512 segments.

The tangents come from the Common Tangents geometry. Each pointer move
looks at the 16 nearest closed subpaths within the snapping tolerance and
keeps the tangents of up to 64 pairs for the rest of the drag.
2026-11-15 16:19:42 -08:00
dotCooCoo 3ac54d7e2a Merge main into feat/object-mosaic-dialog 2026-11-15 16:06:05 -08:00
dotCooCoo 24c0f89ff9 Part of #7840: the Ellipse dialog sets how many anchors the ellipse has
A click with the Ellipse tool opens a dialog with a new Anchors field
under Height, 4 by default. With 4, OK draws the same live ellipse as
before. Any other count from 2 to 1000 draws a closed plain path with
that many smooth anchors spaced evenly by angle, from the left one and
clockwise, with handles of 4/3*tan(theta/4) scaled along each axis and
the path fitted to the typed width and height. The dialog sends the
nearest whole number from 2 to 1000 (4 for an empty field or text that
is not a number). The count confirmed last is kept as the Ellipse
tool's anchors option, and the next Ellipse dialog opens on it.

shape.ellipse takes an optional anchors param (default 4). A number
that is not a whole number from 2 to 1000 gets one error naming that
range, a value that is not a number gets the usual type error, and
nothing is drawn. The MCP draw_shape tool lists anchors for ellipses.

Docs: params text, docs/mcp.md, docs/target-app-parity.md (Shapes).
2026-11-15 12:16:26 -08:00
dotCooCoo 78b1c6bf09 Shapes: draw the circle through three points
shape.circleThroughPoints draws the circle whose edge passes through
three points, as a live ellipse with the current paint, in one undo
step. The points come from `points` or, when it is left out, from the
three selected anchor points: anchor points selected with Direct
Selection, or all the anchor points of a path selected whole. The ends
of selected segments do not count. The result gives the circle's
center and radius. The circle is not pixel-aligned, even while Align
New Objects to Pixel Grid is on, so it stays through the points.

Two points that are the same, or three on one line (twice the
triangle's area at most 1e-10 of its longest side squared), are
refused with a message and nothing is drawn. The center is computed
from the corner opposite the longest side, so nearly collinear points
and points far from the origin keep their precision.

With the Ellipse tool, the first two Shift-clicks place points and the
third draws the circle through the three. After two points the tool
previews the circle through the snapped pointer as a dashed outline;
the preview goes when the pointer leaves the canvas. Once a point is
placed, a Shift-click on the selection's handles or shape widgets
places a point too. Escape, a click without Shift, a drag, a press
without Shift on the selection or a shape widget, and an edit, Undo or
Redo made outside the tool remove the points placed so far. A
Shift-click without a drag used to open the size dialog, as a plain
click does; a plain click still opens it, and so does a Shift-click
while the perspective grid shows with an active plane, so that shape
still goes on the plane.

Docs: docs/mcp.md, ROADMAP. Messages translated in the 24 catalogs
with complete messages.
2026-11-15 11:09:55 -08:00
dotCooCoo 91f3f812c9 Merge main into feat/object-mosaic-dialog 2026-11-15 09:08:24 -08:00
dotCooCoo 69410d99d7 Object Mosaic: a constrained size above 1000000 pt shrinks in proportion
- With Constrain Ratio on, a side worked out above 1000000 pt shrinks to
  1000000 pt and the other side shrinks with it, as a side under 0.1 pt
  grows. An image more than 10000000 times wider than tall (or taller
  than wide) leaves no such size, and the call is refused with an error.
- A percentage typed in New Size is kept at 1000000, the most the
  command takes.
- The #1000 test types the count into Number of Tiles again.
- docs/mcp.md says a size given for the side Constrain Ratio works out
  is still checked, and the new lines are wrapped like the paragraph.
2026-11-15 07:31:45 -08:00
BFlat 8138a6e973 Merge pull request #7814 from dotCooCoo/feat/editing-one-anchor-copies-the-whole-anchor-list
Paths: editing one anchor of a long path keeps one chunk of anchors for undo
2026-11-15 17:31:01 +07:00
BFlat 0473b74e42 Merge pull request #7781 from dotCooCoo/feat/flare-drag-keys
Flare: Ctrl/Cmd holds the center and Up/Down and ~ change the rings while they are placed
2026-11-15 16:40:37 +07:00
dotCooCoo f4dc71aee8 Flare: Ctrl/Cmd holds the center and Up/Down and ~ change the rings while they are placed
While the center is dragged out, Ctrl (Command on macOS) keeps the
center's diameter as the last drag showed it, and the drag sizes the
halo through shape.flare's growth: the halo's radius keeps the ratio to
the pointer's distance that it had when the key went down, within the
Flare Tool Options' 0 to 300 %. Letting the key go sizes the center with
the drag again, and the flare keeps the new growth.

While the rings' end point is placed, Up and Down Arrow add and remove
rings within 0 to 50, and leave the rays as the center drag left them.
Before, they changed the rays in both drags. Each press of ~ (backquote)
sends a new ringSeed. shape.flare takes ringSeed, a whole number below
2^53, and places the rings along the path from a sequence of its own,
keeping their count and sizes and the other parts. seed and ringSeed
given as a fraction, a negative number or a boolean are refused. The
canvas re-hovers the tool when backquote goes down or up, so ~ works with
the pointer held still.

With Rings off, the arrows and ~ do not change the flare in the second
step. Each new flare starts from the options' counts and growth, without
a ringSeed.
2026-11-14 22:39:10 -08:00
dotCooCoo be32d6be89 Align: a Shift-clicked anchor becomes the key anchor that Align and Distribute keep in place
With Direct Selection, the point a Shift-click adds to two or more
selected anchor points is the key anchor. It is drawn as a larger filled
square in a frame, and the Align panel and the Control bar show the key
choice chosen as Align to Key Anchor. The Align buttons move the other
points to its x or y, and Distribute with a spacing places them from it.
A plain click still selects one point alone.

select.key takes {id, anchor} to set it, select.key {} cancels it, and
document.inspect reports it as keyAnchor. It goes when it is deselected,
deleted or left as the only selected point.
2026-11-14 22:14:03 -08:00
dotCooCoo a5493a1cd0 Paths: editing one anchor of a long path keeps one chunk of anchors for undo
A subpath's anchors are now an `Anchors` list held in chunks of up to
256 anchors behind `Arc`s. Copying a path copies the chunk table and
shares the chunks, and editing one anchor copies only the chunk that
holds it, so the undo step of a one-anchor edit no longer keeps a copy
of every anchor of the path. Inserting or removing an anchor copies the
chunk it is in and rebuilds the table. Reads and edits follow the Vec
and slice methods the code used; files write and read each subpath's
anchors as one list, as before, within the same anchor read budget.

The undo memory estimate counts only the chunks the other version of
the path does not hold, and the renderer's kept paths compare only the
chunks an edit copied when they look for moved anchors.

Moving one anchor of an open path of 10,000 or 200,000 anchors
(path.moveAnchor, path.setHandle, path.moveAnchors, a nudge) keeps at
most 48 KiB in its undo and redo steps, where it kept 56 bytes per
anchor.
2026-11-14 21:25:15 -08:00
dotCooCoo a639a0b640 Merge main into feat/object-mosaic-dialog 2026-11-14 19:59:48 -08:00
dotCooCoo cce15bb8ff Merge main into feat/object-mosaic-dialog 2026-11-14 18:31:06 -08:00
dotCooCoo a7c8d28777 Object Mosaic: Create Object Mosaic opens a dialog with its size, ratio and percentage options
Object > Create Object Mosaic... opens its own dialog on the selected
image: Current Size, New Size, Tile Spacing, Number of Tiles, Constrain
Ratio (Width or Height), Result (Color or Grayscale), Resize Using
Percentages, Delete Raster and Use Ratio. It replaces the generic
parameter dialog, which showed only the counts, the spacing and the two
switches.

object.createObjectMosaic takes percentages, constrain and useRatio.
Use Ratio keeps the count on the kept side and picks the other count
whose tiles, spacing taken off, come closest to square, measured along
the image's own sides. A new width or height outside 0.1 to 1000000 is
refused, and the result gives the columns and rows used.

Docs: docs/mcp.md, docs/target-app-parity.md.
2026-11-14 15:25:01 -08:00
dotCooCoo 93a7d532c7 Merge main into feat/rotated-box-scale-reflect 2026-11-14 15:17:16 -08:00
BFlat c0ce77a912 Merge pull request #7663 from dotCooCoo/feat/perspective-auto-plane-positioning
Perspective: Perspective Grid Options has Automatic Plane Positioning
2026-11-15 05:30:40 +07:00
dotCooCoo 163f256418 Perspective: Perspective Grid Options has Automatic Plane Positioning
Perspective Grid Options gets the two Automatic Plane Positioning
checkboxes, Anchor Point of Perspective Artwork and Intersection of
Gridlines. With the Perspective Selection tool, Shift held over an
anchor point of art in perspective, or over a gridline intersection,
with no button down, moves the active plane through that point and
hides the other planes. A plane made active then passes through the
same point. The plane goes back to its place once an object is drawn
on it or attached to it, when the grid hides or no plane is active,
when the file is opened again, and with Escape.

- perspective.plane.infer {at?, tolerance?, clear?} positions, reads
  and clears the held point, which is view state, not an undo step.
- perspective.widget.options takes anchorPoint and gridlineIntersection,
  both on by default and kept with the preferences.
- perspective.plane.move moves a held plane from where it is held.
2026-11-14 12:11:36 -08:00
dotCooCoo 04b90d88d0 Tests: raster effects draw the same twice while another test assigns a document profile
tests::newdoc::a_profile_brings_the_color_profile_its_file_carries and
tests::saveoptions::an_embedded_profile_is_restored give their front
document a non-sRGB RGB profile. That profile becomes the process-wide
active color settings and stays active until a document without one
comes to the front. Every color the engine test process renders goes
through those settings, so the test
tests::rasterfilters::each_effect_changes_the_canvas_and_draws_the_same_twice
could draw the same art in two colors and fail with "<effect> is
deterministic".

The two tests now run again in a child process of the test binary
through a shared helper, tests::in_own_process. The SVG Drop Shadow test
for a non-sRGB working space uses the helper in place of its own copy,
and the GLOBAL doc comment in tests/colormgmt.rs names this route.

The rasterfilters test now checks that the color settings are the
defaults before it draws and that nothing replaced them while it drew.
A test that changes them in the same process makes it fail with "another
test changed the color settings while this one drew".

With the three tests run together (--test-threads=3) on Linux, the
rasterfilters test failed 10 of 10 runs without the child processes,
each time with that message, and passed 10 of 10 with them.
2026-11-14 03:13:56 -08:00
dotCooCoo adc60bfb16 Merge main into feat/rotated-box-scale-reflect 2026-11-13 16:42:07 -08:00
dotCooCoo e51e67116d Path: anchor edits on a long selected path skip measuring it for the canvas check
The check after each edit that the selected objects stay within the
canvas measured the whole of every selected path. Moving one anchor of
a 10,000-anchor path measured all 9,999 segments. A path or compound
path whose anchors and handles are all finite and inside the canvas
range now passes without being measured, because its curves stay inside
their control points. A path with a point outside that range is still
measured, so the check accepts and refuses the same edits as before.

path.moveAnchor to the point the anchor is already at, and
path.setHandle to the point the handle is already at, now leave the
document as it is and record no undo step.

vectorcraft_geom::path::measured_segments counts the segments that
PathData::bounds measures, and the new engine tests use it.
2026-11-13 13:46:30 -08:00
dotCooCoo d7c7b118ec Merge main into feat/rotated-box-scale-reflect 2026-11-13 11:43:40 -08:00
dotCooCoo b1c9783e40 Tests: expect scale to follow the rotated bounding box
A stretch of a turned star along its own box keeps it a parametric shape;
the page-axes stretch that skews it now passes basis "page". The no-op
transform test expects the scale's journal entry to carry its basis.
2026-11-13 10:54:42 -08:00
dotCooCoo cbde1630a1 Documents: closing a background tab keeps the document in front
file.close {index} on a tab other than the current one made the
document now at the closed index current and reset the tool, so the
document the user was working in went to the back. The current
document now stays current, found by its id as document.move does, and
its tool keeps its state. Closing the current tab still makes its
neighbor current.

Docs: docs/mcp.md, docs/target-app-parity.md.
2026-11-13 09:05:44 -08:00
dotCooCoo f81793d671 View: Pixel Snapping Options choose whether Snap to Pixel snaps drawing, moving and scaling
Control bar > Snapping > Pixel Snapping Options... opens a dialog with
three checkboxes: Snap to Pixel While Drawing, While Moving and While
Scaling. OK sets them; Cancel leaves them as they were. While View >
Snap to Pixel is off, the dialog notes that the options take effect once
it is on.

- view.snapToPixel.options {drawing?, moving?, scaling?} reads and sets
  them. They are kept in the preferences as the pixelSnap group, all on
  by default, so turning Snap to Pixel on behaves as before. An unknown
  key or a value that is not a boolean is refused and changes nothing.
  The command has a parameter schema, which raises the API level to 4.
- Drawing covers points the drawing tools place, the Knife's straight
  cut, the Measure tool and the rulers' origin. Moving covers Selection
  and Direct Selection moves, ruler guides, artboard moves and the
  Rotate, Reflect and Shear tools' drags. Scaling covers bounding-box,
  Free Transform, artboard and slice handles and the Scale tool's drag.
  An edit whose option is off snaps as it does with Snap to Pixel off.
- Align New Objects to Pixel Grid and the objects' pixel-aligned
  property do not depend on these options.

Docs: docs/mcp.md, docs/target-app-parity.md.
2026-11-13 01:38:58 -08:00
BFlat 1b9aa07e65 Merge pull request #6995 from dotCooCoo/feat/actions-insert-select-path
Actions: Insert Select Path stores the selected path as a step
2026-11-13 12:27:58 +07:00
dotCooCoo f6d8af3ed6 Merge main into feat/dcs-linked-spot-plates 2026-11-12 19:09:51 -08:00
dotCooCoo 2b975d620e Actions: Insert Select Path stores the selected path as a step
The Actions panel menu has Insert Select Path, after Insert Menu Item.
With one whole path or compound path selected, it inserts a Select
Path step into the action being recorded, or after the selected action
or step. Playing the step selects that path again.

- New engine command `select.storedPath {id, fingerprint}`. The step
  stores the path's object id and a fingerprint of its geometry and
  fill rule ("v1:" and 16 lowercase hex digits, FNV-1a 64). Playback
  selects the path only while it exists unchanged and can be selected;
  otherwise the step fails and the selection stays as it was. A path
  on a locked artboard is refused in isolation mode too.
- Capture refuses an empty selection, several objects, selected
  anchors or segments alone, groups, type, guides, a path selected
  together with ruler guides, a member of a compound path, and hidden,
  locked or template art.
- New UI command `ui.action.insertSelectPath {set?, action?, step?}`.
  Step rows show "Select Path".
- `.vcactions` files that hold a Select Path step are written as
  version 4. Reading accepts versions 1 to 4 and refuses a Select Path
  step with invalid params.
- Rows for the new labels and messages in every catalog.

Docs: docs/mcp.md, docs/target-app-parity.md.
2026-11-12 16:02:00 -08:00
dotCooCoo 18aed1da4e Merge main into feat/dcs-linked-spot-plates 2026-11-12 12:45:18 -08:00
dotCooCoo 7dd161cc49 Place: DCS files link with their spot plates as spot swatches and separate on their own inks
File › Place with Link reads a DCS 1.0 or 2.0 file (an EPS file whose
header names one EPS program per printing plate) as one linked image of
its plates. Each spot plate adds a spot swatch in the CMYK values the
file gives, and the clipping path the file's composite is drawn through
clips the image. document.open, file.place without link or from bytes,
and links.embed refuse a DCS file and change nothing.

- The screen, composite print and exports show the plates mixed into
  CMYK. Separations Preview and print separations show each plate on
  its own ink; a spot plate prints as its CMYK values when spots print
  as process.
- links.list answers the format DCS, and with dcsTransparency marks the
  DCS images that are transparent or overlap transparent objects (the
  Links panel menu's Show DCS Transparency Interactions).
- swatch.unused leaves out a spot swatch while a DCS image has a plate
  of its ink.
- links.update and links.relink read the plates and the clipping path
  again, and the link shows as modified when one of its plate files
  changes or is gone.
- The plates go on the first plate's pixel grid, grown to hold every
  plate where it prints; a plate of another size or position is
  resampled onto it.
- A file may name 64 plates, a plate file may be 1 GB, and the plates
  together may hold 512 MB of ink amounts. A file naming more plates is
  an error.

Docs: docs/mcp.md, docs/target-app-parity.md, docs/file-format-parity.md.
2026-11-12 09:30:20 -08:00
dotCooCoo fe34c2b818 Merge main into feat/custom-arrowheads 2026-11-12 09:23:20 -08:00
dotCooCoo 5e80810605 Merge main into feat/custom-arrowheads 2026-11-12 05:00:21 -08:00