- The Blend Options dialog sends the spacing, count or orientation only
when it was set in the dialog or differs from the first blend's, so
OK on several blends no longer copies the first blend's spacing and
orientation onto the others.
- object.blend.options: a spacing mode without a count keeps the count
of a blend already in that mode. An orientation other than page or
path, a spacing that is not a string, and `value` without `spacing`
are errors (orientation also in object.blend.make and the options new
blends start with).
- The Blend panel dims Type and Ramp while any selected blend has no
spine, since the command refuses easing for such a selection.
- Tests check the live preview while a Ramp or Shift drag is under way.
Supersedes #8022 by ruchirguitar.
select.magicWand searched lists in three places: paintable looked up
each object's parent in the list of compound paths, add mode looked up
each hit in the selection, and subtract mode looked up each selected
object in the hits. These lookups now use HashSets. The output is still
built by walking the lists, so the wand selects the same objects in the
same order as before.
A test compares paintable, added, subtracted and select.magicWand in
set, add and subtract mode with copies of the earlier searches on a
20,000-path document. An ignored release-build probe times both.
object.blend.options wrote the first selected blend's spacing, orientation,
type, ramp and shift onto every selected blend, whatever the call gave. Each
blend now takes only the values given and keeps its own for the rest, through
one closure used for the selection and for `id`.
- `id` edits that blend alone. A hidden or locked blend and an object that
is not a blend are errors, and the blend's own spine decides whether
easing is allowed.
- A call that changes no blend records no undo step.
- The Blend panel's Ramp and Shift sliders share one helper: a drag
previews on the canvas and records one undo step on release, instead of
one per frame.
Builds on #8022 by ruchirguitar.
Docs: docs/mcp.md, docs/target-app-parity.md.
A trim checked and changed the selection once for every trimmed path
and every piece, and each check or removal went through all selected
objects, so a trim of thousands of selected paths spent time
quadratic in their number on the selection alone. The command now
reads the selection through a set and removes and adds objects once
at the end. The resulting selection is the same as before, including
object order, the key object and key anchor, the direct-selected
anchors and segments, and the fields that a change to the object
selection clears.
Under Include Bleed, a PDF row that sets no bleed now keeps the bleed values a saved PDF preset writes out and turns on useDocument, instead of replacing the whole bleed object. Its file key then matches a row of the same preset that asks for the document's bleed, so the two rows write one PDF.
When the import refuses a file's PDF part and its editing data can't be
read either, the error named only the PDF part. It now adds "its editing
data couldn't be read either (<why>)", as layers already do
(crates/eps/src/import.rs). The reasons come from the editing data
reader (a size limit, damaged compression) and from the private data
streams (larger than 256 MB, another filter or decode parameters,
damaged zlib data). A file without editing data, and an open with pages
picked, layers off or the editing data off, keep the PDF part's error.
Part of #4366.
select.anchorsMany, which the Direct Selection and Group Selection
marquees, the Lasso and Smart Pen send, checked and changed membership
through Selection::contains, add and remove for each item, each a scan
of the selected objects. It now keeps the selected objects in a map
while the items run and writes them back once. The objects, their
order, the anchors, segments, key, key anchor and the other selection
fields come out as before, repeated ids and ids deselected and
selected again included.
Tests compare the result with the item-by-item loop for every mode,
four starting selections and fifteen item lists, and bound the passes
over the selected objects. An ignored benchmark times both loops on
2,000, 20,000 and 50,000 rectangles.
A graphic style dragged from the panel onto the New Graphic Style button
runs Duplicate Graphic Style. The button takes the drop with no art
selected and is outlined while a style is held over it. A dragged style
that is highlighted brings the other highlighted styles, copied in panel
order in one undo step, and the copies are highlighted.
graphicStyle.duplicate now adds the copy at the end of the list instead
of right after its source, for the panel menu's command and the drop.
The list's drop zone no longer reaches over the footer when the list is
shorter than 220 pt, so a style released on New Graphic Style or Delete
is not moved to the end of the list.
Clear with `ids`, which Cut uses for the objects it copied, removed each
id from the selection with its own scan of the selected objects. It now
calls Selection::remove_all once, which gives the same selection.
With 50,000 objects selected and all of them cut, the selection step
takes 5.5 ms instead of 572 ms (release build, median of 7 wall-clock
runs, measured while other builds were running). The new tests compare
the result with removing each id in turn, including Undo and Redo, and
an ignored benchmark times both.
With Link, File > Place now places an EPS file, a PostScript file and a
PostScript .ai as a linked placed document, but the Place dialog still
counted them as other files, so Link's tooltip did not say they become one
locked object, and the dialog test expected a PostScript .ai to be
embedded.
- `is_vectorcraft_file` counts an EPS, EPSF or PostScript file on disk, and
a PostScript .ai, as a document, and leaves out a DCS file, which is
placed as a linked image.
- Where the platform reads part of a file, it reads only the file's start
and tells a DCS file from it with `place::head_is_dcs` (the check Links
uses), binary EPS headers included.
- The dialog test now checks the .ai, .eps and .ps cases, the bounded read,
DCS files plain and behind a binary header, and a file named .eps that
isn't PostScript.
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.