A global or spot color that a library pattern's art brings under a
numbered name no longer takes a name the library gives another swatch.
Before, adding a pattern whose art uses "Ink" to a document with another
"Ink" brought the color as "Ink 2" even when the library has its own
"Ink 2"; adding that library swatch next then came in as "Ink 2 2". The
brought color now takes the next free name the library does not use
("Ink 3"), and every paint linked to it follows the new name, so adding
the library's "Ink 2" next adds it under its own name and adding both
again adds nothing.
A color the pattern's art brings or takes is the color a library tint
or gradient links to only when it has the library color's paint and its
process, global or spot kind, as for the other lookups in the same add.
The test a_numbered_copy_named_like_another_library_color_is_found now
makes the blue "Ink 2" itself, as an earlier version's pattern add left
it, since a pattern add no longer gives that name.
A library tint or gradient counts as already in the document only when
each color it links to is there. When the document's tint of that name
links to a color the document no longer has (deleted without unlinking),
the color comes back under its own name and is listed in `added`.
A picked pattern the document already holds keeps the copy of a color
its art takes (a numbered copy the library also names), and the picked
tints and gradients of that color link to it, so adding the pattern and
the tint again adds nothing. Without such a pattern, a numbered copy the
library also names stands for that library swatch alone.
docs/mcp.md also states that a pattern pasted with Merge for some colors
and Add for others is added again as a copy.
swatch.library.add linked a library tint to the wrong color in two cases.
When the document had a process color with the same name and paint as the
tint's global color, the global color counted as already present and the
tint linked to the process color. When a tint was added without its global
color and the document had another swatch of that color's name, the tint
linked to that swatch.
- A library color counts as already in the document only when the
document's color of that name is the same kind: process, global or spot.
A global color whose name the document gives a process color now comes
in under a numbered name, and its tints link to that copy.
- A global or spot color that an added tint or gradient links to, and that
the document does not have, now comes in with the tint or gradient. It
keeps its own name when that name is free and gets a number otherwise.
added lists it after the picked swatches.
- A library tint is not the document's tint of the same name and paint
when the document's swatch of the base's name is another color or kind.
- A tint that a pattern brought is used for a picked library tint only
when the color it links to is the library color's kind.
When a library tint waits for a color that a pattern's art brings,
swatch.library.add learns the color's name by importing the pattern into
a copy of the document. The import into the document now confirms those
names: when it gives a color another name, or none, the tints linked
from the copy are linked again.
- library.use and Add to Swatches report an error from the import that
merges a pattern's colors instead of falling back to adding them.
- The params text, docs/mcp.md and docs/target-app-parity.md say that a
tint or gradient links to the numbered copy its global or spot color
comes in under or already has, and name a gradient test.
- The new code uses the HashMap import, and one helper relinks the
added tints and gradients at both places that did it.
A library tint or gradient whose global or spot color comes in under a
numbered name now links to that copy whichever order the swatches are
picked in, when the color was added by an earlier call, and when a
pattern's art brought the color or took the document's copy of it.
Adding the same tints again finds the ones added before.
- Each tint's or gradient's color is looked up for itself before
anything is added, past a process swatch of the same paint and past a
color group of that name. A numbered copy that the library's own
swatch of that name is stays that swatch's, and a new copy skips the
library's other names.
- A tint links to a global or spot color of the same kind only, and to
a color this call picks rather than to a copy a pattern took.
- Links are set as soon as the color's name is known. A tint waiting
for a color that a pattern's art brings learns its name from an
import into a copy, so the pattern does not add a second tint.
- A swatch a pattern brought takes a picked swatch's place only when
its colors link where the picked one's do.
- A stop linked to the Registration swatch counts as linked.
- library.use, Add to Swatches and the reuse check share one import
probe (patternlib::probe_import), and the probed copy is kept instead
of importing a second time.
Docs: docs/mcp.md, docs/target-app-parity.md.
Since the change that brings a library pattern's global and spot colors
under a numbered name ("Ink 2") when the document gives the name another
color, adding the same pattern or color again added more copies, and
Use Library Item still linked a pattern's art to the document's own
color of that name.
- A library color whose name the document gives another color is the
document's numbered copy with the same color, so adding it again adds
nothing. A numbered name that the same call also picks is not shared.
- A pattern the document holds with its art linked to the document's
own color of a name, as pasting with Merge leaves it, is reused
instead of coming in again as "Squares 2".
- `added` lists the colors a pattern brought, after the picked swatches.
- A library tint added with its base color links to the base's name in
the document, and a later add finds it there.
- library.use brings a pattern's colors the same way.
Docs: docs/mcp.md.
* Text styles panel: add item right-click context menu (Options, Duplicate, Delete, Redefine)
* fix(text-styles): require text target for clear overrides and update parity docs
* Properties panel: add contextual Quick Actions for text (Create Outlines, Retype, Find and Replace)
* Properties panel: address review comments on Retype reveal idempotency, test assertions and parity docs
- Forward secondary clicks on name label links for stroke/fill and effect rows
- Enable Reduce to Basic Appearance when any selected subject needs reduction (including compound path children)
- Add headless regression tests for label context clicks and multi-selection reduction
- Update M14 roadmap entry and UI parity evidence, and clean conflict markers in ui-parity.md
* Adopt the shared AGENTS.md (RFC-0072) and test rules (RFC-0071)
* Drop a restated rule from This repository
* Remove the cleanroom xtask command, which does not exist
* AGENTS.md: correct the repository facts
The desktop app's platform modules allow unsafe; list them.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: FredApps <FredApps@users.noreply.github.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: FredApps <153173854+FredApps@users.noreply.github.com>
The monitor list for floating panels now carries each monitor's work
area: rcWork from GetMonitorInfo on Windows, and visibleFrame on macOS,
turned into the top-left origin and physical pixels of the monitor's
rect. The work area is converted to points with the same scale and zoom
as the rect, and craft-ui uses it to decide whether a reopened panel's
title bar can be grabbed and where to move it. A work area with no width
or height is left out.
Restoring the main window now keeps it inside its monitor's work area
too, so a window saved at the top edge of a monitor with a taskbar along
its top opens below the taskbar, and a window taller or wider than the
work area is made to fit it, with room for a system title bar and
border when the window has them.
On Windows the panel list stays empty when the monitors have different
scale factors, as before, and a build without the wgpu feature reads no
work areas. Linux and the BSDs keep the whole monitor rect.