While guides were locked, a guide path inside a group was still touched by
a selection marquee, so the marquee selected the group and moving the
group moved the guide (#8538). Clicks already skip guides (#3074).
- hit: marquee_in_view and enclosure_candidates take skip_guides; the
Selection, Direct Selection, Group Selection and Enclosing Lasso tools
pass !cx.guides, and the marquee then touches no guide path at any depth.
- doc: Scaling::keep_guides leaves the guide paths among a group's,
layer's or Intertwine group's children in place, as a ruler guide in a
transformed layer already stays.
- engine: transforms (apply_transform), Transform Each and Align and
Distribute set it while Lock Guides is on; a copy takes a copy of the
guide with the copied art and leaves the original.
Fixes#8538
The Pressure Sensitive test now requires finite anchors and a positive,
finite width at both light and heavy pressure before it compares them.
The current brush-library inventories in docs/target-app-parity.md,
docs/gaps.md, docs/roadmap.md and docs/ui-parity.md list Pressure
Sensitive and count eleven built-in libraries.
The whole-outline check tests points along every edge, so outlines with
the same corners joined another way do not match; past a work limit it
rejects. Face keys another Retype kept meanwhile are reused and charged
once. The fonts parameter test uses outlines that would match. The parity
note states the search limits.
An image placed from a PSD or PSB file that names a clipping path comes
in a clip group of that path, and its image is kept as a PNG (or, for a
CMYK file, a TIFF) that holds the path. Unembed writes that file as
stored, but the file was read back without the path, so Unembed turned
the clip group into a plain group, and File > Open, File > Place,
Relink and Update Links of the written file gave an unclipped image.
The shared loader now reads the path a PNG or TIFF keeps, so these
commands keep the clip group, for Unembed with a path and with a folder.
With Use Preview Bounds on, W and H measure a stroked path from the
outside of its stroke, while the Dimension tool's Linear points only
snapped to the path's anchors, on the stroke's centerline. A dimension
between the corners of a 12 x 6 mm rectangle with a 0.4 mm stroke then
read 11.6 x 5.6 mm.
- With Use Preview Bounds on, a Linear click within 8 pixels of a corner
of the preview bounds of a path or compound path (strokes and effects
included) lands on that corner instead of on that object's anchors,
whatever the snapping options. An anchor of other art nearer the
pointer than the corner takes the point, and a corner that is also an
anchor takes the anchor.
- The point is held against the anchors of the path whose bounds reach
that corner, also when the corner lies far from the path or on another
path's segment. It moves with the path; a later change to the stroke
weight does not move it.
- A press on such a corner picks it when the pointer moves a few pixels
before the release, as on an anchor.
- Hovering by such a corner shows the anchor ring. The ring now also
shows when the pointer is exactly on the point a pick lands on, which
it did not for the end of a dimension's line.
Docs: docs/dimensions.md, docs/target-app-parity.md.
tool.setOption checks every option with the tool's check_option before
it sets any (#7366). The Tangent Circle Tool now accepts `radius` from
0.01 to 1000000 pt and gives an error for a value outside that range,
one that is not a number, or any other option. Without the check the
tool's options dialog could not set the radius.
Part of #7178.
With no place to go on from, the dialog left out edit.findNext's from, so the search went on after the selected type object and passed over its matches: after Find selected a type object, changing the Find text skipped the matches in it. edit.findNext now starts at the first match for a null from, and the dialog sends one.
Answers the second CodeRabbit review on #8549.
- A stroke that goes over no filled glyph (stroked type of its own) and
the start and end of an ActualText span now end the stroke pass
(Builder::end_fills): the held strokes are matched, the parked lines
finished and the open line's fills closed, so a later stroke can't go
over an earlier fill and a later span keeps its own replacement text.
- ActualText fills are ordinary entries in the line's fill list, and
span strokes are held and matched in replay order like any other, so
an A/B/A TJ in a span strokes the replacement. The actual_fills map,
stroke_parked and has_actual_fill are gone.
- Past MAX_HELD, the held strokes are matched to the first run of
glyphs filled one right after another that they go over
(Builder::replayed), with bounded work, instead of each to its first
match, which could reach an earlier operator's fill.
- Docs state that past 64 lines in one operator each part stays a
filled object and a stroked one.
- With the Artboard tool chosen, align.toKeyObject fails with "Align to
Key Object isn't available with the Artboard tool" instead of "no key
object": the selected objects can still have a key in that state. The
message has a row in every catalog that has "no key object".
- Align to Key Object is off in Object › Align and the Align panel when
the topmost selected object is inside another selected object, the
case where choosing it already failed.
- The align.toSelection params text says the selected objects keep
their key with the Artboard tool chosen; ui_catalog.rs regenerated.
- A test pins Align to Key Object with a key anchor: checked, the menu
name kept, and the key anchor kept.
The level a new dimension line lands on now comes from the dimension
lines in the document before the dimension's first preview, so its own
preview is never a level. A dimension drawn earlier between the same two
points now acts as a level as well; before, every dimension of those
points was skipped.
- Of two lines on one level, a line the pointer lies across wins over a
line whose end is nearer the pointer.
- A dropped press while placing removes the level guide with the
preview.
- The reach uses the Smart Guides snapping tolerance helper.
- docs/dimensions.md says the rule applies to a dimension anywhere in
the document.
- The tests are split by behavior, with new tests for the same points,
pointer moves in small steps, the guide after a dropped press and
with Alignment Guides off, and the tie-break.
The preview segment from an anchor with an outgoing handle was drawn as a
quadratic curve through that handle, while a click appends a corner
anchor, which makes the cubic curve that leaves along the handle and
arrives without one. The segment changed shape when the anchor went
down. The rubber band now draws that cubic curve.
Part of #8296.
recolor.apply with `group` rewrote the group by place: the new colors went
to its swatches in order, so a gradient, pattern or None swatch in the group
took a color or was removed, at OK and in the live preview.
The group's colors, from the rows or from `groupColors`, now go to its color
swatches in order, and every other swatch keeps its place and its paint.
`groupColors` counts the color swatches only, as the dialog already does
when it lists a group's colors. swatch.editGroup is unchanged.
`transform` read `reflect` with `as_str`, `copy` with `as_bool` and
passed `origin` through unchecked. A `reflect` of `42` or `true`
skipped the reflect step and reported success for the steps before it,
a `copy` of `"yes"` transformed the original instead of a copy, and an
`origin` that was not two numbers fell back to the selection centre.
The handler now checks all three before it selects `ids` or runs a
step, and returns an error that names the argument. A null value of
any of the three is left out. The tool description and the
`transform` row in docs/mcp.md say so.
Fixes#6448
The Command Palette entry said a result matched through a typo comes
after every result the query matches without one. A result the query
matches only through its description ranks below a typo match, as
a_description_match_ranks_below_a_typo checks. The sentence now limits
the comparison to name, menu path and id matches and states that typo
matches come before description-only matches.