- A path made into a guide draws without its strokes or effects, so its
preview bounds give no corners.
- The members of a compound path draw with the compound path's own
appearance, so only the compound path's preview bounds give corners.
- Another path's anchor right on a preview bounds corner takes a click
on the anchor that corner stands in for, so the point links to that
path.
- A corner that its path cannot hold a point at, as on a stroked dot
whose anchors all coincide, is not snapped to, so a click by the dot
picks its anchor.
- The pointer test before measuring a path includes the right and
bottom edges, as the 8 pixel distance test does.
Docs: docs/dimensions.md and docs/target-app-parity.md name paths made
into guides and compound path members among the art without corners.
A corner of a path's preview bounds took a Linear pick from every anchor
of its own object within 8 pixels, so the top, left, right and bottom
anchors of a small stroked circle, and the anchors of a rotated stroked
shape when zoomed out, could no longer be picked.
- The corner now takes the pick only from the holding path's anchor at
the same corner of the object's geometric bounds. Any other anchor,
of that object or of other art, that is nearer the pointer takes the
point, and the nearest anchor wins a tie as the topmost.
- The path that holds a point picked on a corner is kept from the pick,
instead of being worked out again from the point's position, so a
point that only happens to lie on a corner links to what is under it.
A path deleted between the clicks holds nothing.
- A corner of a compound path whose supplying member is hidden or
locked is not snapped to.
- The hovering test checks the "anchor" label at the corner, and a new
test covers the anchor ring right on the end of a dimension's line.
Docs: docs/dimensions.md and docs/target-app-parity.md say that only the
four corners are snapped to, by VectorCraft's own rule, not the edges of
the preview bounds, a group's own strokes or effects, or type; that a
corner point starts no construction guides; and that the dimension
measures W and H when it is drawn, since a later stroke weight change or
a scale with Scale Strokes off moves the point with the anchors.
docs/dimensions.md now says that the other dimension, and every layer
and group it is in, must be visible and unlocked, and that the tool
reads at most 20,000 visible, unlocked objects, from the frontmost back.
The transform tool treats a null reflect, copy or origin, and a null
numeric step, as given, but its inputSchema allowed only the non-null
types, so a client that validates against the schema could not send
them. Each of those properties now also allows null. The transform row
in docs/mcp.md says a step that is neither a number nor null is an
error, and that a null dx or dy counts as 0 and still runs the move.
Placing an angular, radius or diameter dimension no longer reads the
lines of the dimensions in the document, which only a linear dimension
can line up with. A linear dimension still reads them with Smart Guides
off, so it lines up when Smart Guides are turned on while it is placed.
docs/dimensions.md no longer says the level can come from a dimension
anywhere in the document: the tool reads at most 20,000 objects.
A transform no longer leaves locked guide paths in place: a guide in a
group moves with its group again, as on main. Keeping them put made
Align, Transform Each, the pixel-grid snap and Objects on Path measure or
place art the transform did not move. Scaling::keep_guides and its
engine wiring and test are removed.
The marquee rule now covers the rest of the selection side, while guides
are locked or hidden:
- the guide rule goes down the walk as an explicit Rules value instead
of a thread-local guard;
- an Enclosing Lasso loop does not take a compound path for its guide
contours;
- an enclosing marquee measures a group without its guide paths
(Node::without_guides);
- Direct Selection's marquee takes no anchor or crossed segment of a
guide path.
Docs: the Guides area row, its evidence entry and the M1 row describe
the marquee behaviour; status lines and revision rows say a guide in a
group still moves with it.
Answers the fourth CodeRabbit review on #8549.
When a fill pass finishes lines beyond MAX_PARKED, their unstroked
glyphs are recorded (bounded at 4096). The first stroke after that
which could have gone over one of them ends the stroke pass, so a TJ
over more than 65 lines that comes back to where it began stays a
filled object and a stroked one for each part, as documented. Any
other first stroke drops the record, so type after an overflowing TJ,
filled only or not, is matched as before.
MAX_HELD's doc now says that one operator filling the same run of more
than 4096 glyphs twice at the same places is matched as well as it can
be: the reader tells no operator's start.
Answers the third CodeRabbit review on #8549.
- stroke_last no longer restyles the glyph drawn last once a boundary
(end_fills) closed it: a stroke after an ActualText span no longer
strokes its replacement text. A glyph stroked again where it was just
drawn still stays one object.
- Past MAX_HELD, the held strokes go over the last run of consecutive
fills they match with room for all of them, not the first, so a long
stroke pass no longer takes the same glyphs an earlier operator
filled at the same place.
- Docs: the limit is 64 kept-back lines plus the open one, so a TJ over
up to 65 lines stays filled and stroked.
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.
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.
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.