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.
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.
While a Pen drag past the drag threshold shapes a handle, the Info
panel shows the change in x and y, the distance and the angle from
the anchor to the handle's end: the outgoing handle of a new, added
or last anchor, and the incoming handle of the first anchor when the
drag closes the path. Shift gives the constrained handle and Space
moves the anchor with it. The readout clears on release, a dropped
press and a tool change.
The Enclosing Lasso Tool joins the Lasso group in both shipped
toolbars, right after the Lasso, and stays in Object › Plug-ins ›
Enclosing Lasso. The All Tools drawer lists it once, under Select, and
Edit › Keyboard Shortcuts › Tools lists it once. It has no default
shortcut, and the Lasso keeps Q. A toolbar the user already edited
keeps its saved layout; Reset Toolbar adds the tool.
Fixes#6117
P, a click on the active Pen's button and `tool.select {tool: "pen"}`
now end the path being drawn through the same cleanup as Escape: the
path stays open and selected (a path inside a compound path leaves the
compound path selected), the Pen stays chosen, no undo step is added,
and the next click starts a new path. An anchor or handle being dragged
is committed first. With no path being drawn nothing changes.
Before this change the Pen kept drawing the same open path when it was
chosen again; the Blend test that stated that rule now checks the new
behavior.
With Rectangle, Rounded Rectangle, Ellipse, Polygon or Star active, a
double-click on a visible corner widget of a selected live rectangle or
polygon shows and selects the Transform panel (window.panel.activate),
wherever it is: closed, docked behind another tab, floating, in an icon
column or in a dock hidden by Tab. A second double-click keeps it on show.
The tool, the selection, the document and the undo history stay as they
were. Pie widgets, spots off the widgets, Line Segment, plain paths and
hidden or angle-excluded widgets do nothing; the Selection and Direct
Selection tools keep their double-click behavior.
Tools return the new Action::Panel, which the engine forwards as
UiRequest::Panel; the desktop app activates the panel, and a headless
pointer_gesture reply carries {"panel": id} in its requests.
Docs: docs/ui-parity.md (#5477 row, also correcting its statement that the
bounding-box handles scale only with the Selection tool) and
docs/target-app-parity.md.
The Trim at Crossings Tool joins the Scissors group in both shipped
toolbars, after the Knife, and stays in Object › Plug-ins › Path
Precision Tools. The All Tools drawer lists it once, in the Scissors
group, and Edit › Keyboard Shortcuts › Tools lists it once. It has no
default shortcut. A toolbar the user already edited keeps its saved
layout; Reset Toolbar adds the tool.
The Knife's cursor is now drawn as a knife, its blade's point on the
hotspot, instead of borrowing the crosshair. The Knife tool and the Trim
at Crossings Tool both show it. Use Precise Cursors still shows the
crosshair.
Suggested by erolka and leanma.