stroke.weightUp and stroke.weightDown now go through bucket_color_params and
item_target, as stroke.set and stroke.setAdvanced do, instead of skipping
item_target while the Live Paint Bucket is active. Each command still
refuses `target` and `aligned` with any tool, since neither is one of its
parameters.
- live_paint_bucket_refuses_a_bad_target_or_aligned (renamed from
live_paint_bucket_refuses_a_bad_target) runs with the Selection tool and
with the bucket, and adds stroke.set, stroke.weightUp, stroke.weightDown,
paint.swap and paint.default.
- live_paint_bucket_paint_and_stroke_commands_leave_the_selection_unpainted
adds stroke.set with `ids: null` and stroke.weightUp with `id: null`.
- The params text of the bucket-routed commands says a null ids or id
counts as none.
- docs/mcp.md names gradient.presets.apply next to paint.editGradient for a
picked symbol part, lists when a stop selected on the bucket's gradient is
deselected, and rewraps the two long lines.
- While the Live Paint Bucket is active, a paint or stroke command with
a null ids or id goes to the bucket's colors, as one without them does.
Before, it painted the selection, since other commands read a null ids
or id as no target.
- A bad target or aligned value is refused while the bucket is active,
as it is with any other tool, instead of changing the bucket's colors.
- stroke.weightUp and stroke.weightDown no longer read the selection's
active Appearance row while the bucket takes the weight, as stroke.set
and stroke.setAdvanced already do. The row was not used in that case.
- The params text of gradient.selectStop says that, while the bucket is
active, it selects a stop of the default paint's gradient, also with an
object of a symbol instance picked. docs/mcp.md says the same, and that
paint.editGradient without ids, id or item then changes the bucket's
gradient.
- docs/mcp.md again says that another tool chosen after the bucket keeps
its colors until a command or a new selection changes them.
While the Live Paint Bucket is the active tool:
- each preview in one interaction starts from the colors the
interaction began with, so previewing paint.swap twice and committing
swaps once;
- a gradient stop selected on the selection's gradient is not selected,
and one selected on the bucket's gradient is not selected after
another tool is chosen;
- gradient.selectStop selects a stop of the bucket's gradient even
with an object of a symbol instance picked;
- gradient.presets.apply picks the fill or stroke by the active proxy,
not by the selection's active Appearance row;
- stroke.set and stroke.setAdvanced no longer read the selection's
Appearance row;
- the Stroke panel's Align Stroke buttons are on, as with nothing
selected, matching stroke.set, which takes every alignment.
The params text of paint.sampleColor, gradient.presets.apply,
stroke.set, stroke.weightUp and stroke.setAdvanced, the set_paint note
and the Live Paint paragraph of docs/mcp.md now describe this, and say
that the bucket takes only the color and weight of the stroke for new
art.
With a Live Paint group selected and the Live Paint Bucket active,
choosing a fill color (a swatch, the Color Picker, the Fill box) painted
the whole selection, so every face and edge of the group took one color
before the bucket painted anything.
While the bucket is the active tool and no ids, id or item are given:
- paint.setFill, paint.setStroke, paint.none, paint.lastColor,
paint.lastGradient, paint.editGradient, paint.invert,
paint.complement, paint.swap and paint.default change only the
defaults, the colors the bucket paints with, and record no undo step;
- stroke.set, stroke.weightUp, stroke.weightDown and stroke.setAdvanced
(without a brush) change only the stroke for new art;
- the Fill and Stroke proxies, the Stroke panel and its Profile list
follow those defaults, as they do with nothing selected;
- New Art Has Basic Appearance off no longer copies the selection's
appearance into them after a command;
- canceling a Color Picker preview puts the bucket's color back.