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.
- 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.
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.
main's gate fails french_catalog_uses_nonbreaking_prose_punctuation on
the "{pos} of {total}: {name}" row of fr.tsv, added by #8017, which has a
plain space before the colon. The row now uses U+00A0 there.
Open #8053 fixes three other rows that main already has right, so it
does not clear this failure.
The Contextual Task Bar and the Control bar check, each time they are
drawn, whether the selection holds a color that Recolor Artwork can
change. The check walked the whole subtree of each selected object even
after the first color, so with one large group selected, the check read
every paint in the group.
- Node::try_walk visits in walk's order and ends at a ControlFlow::Break.
- swatches::node_has_colors stops at the first color node_colors would
visit; node_colors now runs the same visitor without stopping, so the
two read the same nodes and paints in the same order.
- has_colors in the task bar uses node_has_colors.
The result is the same for every selection. On one group of 100,000
paths, the check takes 16 ns instead of 14.5 ms when the first path is
filled; when only the last path is filled, or none is, it costs about
what the full walk costs.