The Blend panel dimmed Type, Ramp and Reverse Spine only when a selected
object was itself a blend without a spine. With a key of each of two
blends selected through Direct Selection, the controls stayed enabled
while the commands, which act on each key's blend, refused the edit.
The panel now checks each selected object's nearest blend, as the
commands resolve it.
EPS export writes a gradient whose stop links to a spot swatch named
Cyan, Magenta, Yellow or Black and carries process plates in process
colors, with a warning. The stop_inks doc comment and the progress-doc
line now say so.
A fill, stroke or gradient stop links to a swatch by name, and the first
swatch of that name is the one it prints from. The plate list added a spot
plate for every spot swatch, so a spot swatch after a process swatch of the
same name got a plate that printed nothing, while art linked by that name
separated as process. The plate list now takes only the first swatch of
each name.
A spot swatch named Cyan, Magenta, Yellow or Black had no plate of its own
and printed nothing on the process plate of its name. Art linked to it now
prints its tint on that process plate, as PDF and EPS export write it, and
a gradient stop's own process plates print beside it.
Double-clicking the Arc tool opens Arc Segment Tool Options, which now shows
the arc below Fill Arc and redraws it as the lengths, Reference Point, Type,
Base Along, Slope and Fill Arc change, ui.dialog.set included. The picture is
the arc shape.arc draws from the options OK sets, fitted into a 160 x 120 frame
with its proportions kept, in the current stroke (black when there is none),
filled with the current fill when Fill Arc is on, turned by General > Constrain
Angle, with a mark on the reference point. A gradient or pattern stroke or fill
shows as gray. OK still only sets the options and draws nothing; the click
dialog has no picture.
- 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.
A Shift-click with the place cursor now opens the current file's import
options (Text, DXF, Place PDF or Place PSD) before it is placed, whether
the cursor was loaded with Show Import Options on or off or by
file.place.queue. OK places the file at the click and the cursor moves to
the next file. The options the cursor was loaded with for the file's
format are put aside so the dialog opens, and are used when no dialog
opens for the file (a PNG image, a one-page PDF, a linked PSD file). A
Shift-drag places at the dragged size, as a drag does. Headless, where no
dialog can open, a Shift-click places as a click does.
The place tool marks a Shift-click's file.place with
showImportOptions: true.
Docs: docs/mcp.md, docs/target-app-parity.md.
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.
The parity line said a soft-edged gray stroke running out of black loses
"3 or 4 pixels" where it meets black. It now says 3 or 4 of the 16 pixel
centers along its middle nearest black, as docs/image-trace-adjustments.md
and the test count them.
In docs/image-trace-adjustments.md, gray near black on blurred edges now
traces gray at fewer of its pixel centers instead of "losing pixels", a
wider band loses some or most of its gray instead of part of it (bands 3
and 4 pixels wide at a blur of 1 pixel keep about 60 of 336), and the
paragraph is wrapped to the file's line width.
The band test now also sums the samples traced gray for bands 3 and 4
pixels wide blurred by 1 pixel (about 60 of 336 over the three grays;
16 without the sharp-edge stop) and for bands 4 pixels wide blurred by
3 pixels (about 39 of 192).
across_edge decides from the first step alone whether one side's edge is
sharp, so each side's path is walked once. On 856 code-drawn band and
stroke cases and 39 images the results are the same as before.
The docs count pixel centers instead of pixels, write "0.6 pixels"
throughout, give the parity line's band claim its bound of 1 in 16, and
state again that a light gray stroke 6 or 8 pixels from black keeps its
gray because its pixels do not reach black in 5 steps.
Text on more than one line is placed a line at a time at every
alignment, and each line splits where an advance that tracking can't
give puts its characters, as a single line does. An underline or
strikethrough also runs on to the end of a line's last advance when
tracking can't reach it.
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.
Direction Handles cleared the selection and then added each path on its
own, and each add searched the paths already selected, so building the
selection took time that grows with the square of the path count. The
command now selects the paths with one Selection::set call and adds the
anchor sets in one extend. The selection is the same: paths keep their
order, a repeated path keeps its first place and its last anchor set,
and the side fields are cleared as before.
crates/engine/examples/direction_handles_bench.rs times both ways on the
same paths in one process. With 20,000 four-anchor paths, building the
selection takes 1.9 ms of thread CPU time against 69 ms one path at a
time.