- 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.
With the Flare tool, an Alt-click (Option-click on macOS) now draws a flare
centered at the click at once, with the tool's current options, instead of
opening the Flare Tool Options. Alt counts when it is held as the button goes
down; a drag with Alt draws the flare in two stages as before. While the
perspective grid shows with an active plane, the flare is drawn on that plane
from the click, as the dialog's OK draws it, and a click the plane cannot take
reports the error. A plain click still opens the dialog.
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.