With a sublayer isolated, Exit Isolation Mode now isolates its parent layer
and selects the sublayer, so repeated use goes up one layer at a time and
leaves isolation mode from the top-level layer, as the help page describes:
https://helpx.adobe.com/illustrator/desktop/manage-objects/select-objects/isolate-objects.html
This applies to the Layers panel menu item, the isolation bar's back arrow,
the Control bar button, the canvas context menu, a double-click outside the
art and object.exitIsolation {}. Before, each of them left isolation mode in
one step.
- object.exitIsolation takes all (default false); all: true leaves
isolation mode from a sublayer at any depth. Any other value is an error.
- Esc and the top-level layer's crumb on the isolation bar pass all: true,
so they still leave in one step. A sublayer's crumb isolates that
sublayer.
- A hidden or locked parent layer is not isolated; the call leaves
isolation mode. A step up records no undo step. Groups keep their rule.
The Shear dialog's Axis now has Angle beside Horizontal and Vertical, with
an Axis Angle field (0 degrees when the dialog opens) that takes input
while Angle is chosen and keeps its value otherwise. object.shear takes a
numeric axis from -359 to 359 degrees, a line on the page measured
counter-clockwise from horizontal, as object.reflect's numeric axis is; the
shear angle stays a separate value. 0 shears as horizontal and 90 as
vertical. An angle outside the range, a number written as a string, or any
other value is an error naming it, and nothing changes.
Behavior reference: https://helpx.adobe.com/illustrator/desktop/manage-objects/reshape-transform-objects/shear-objects.html
describes the angled axis and its range. The counter-clockwise direction
and the 0 degree start are VectorCraft's own.
Docs: docs/mcp.md, docs/target-app-parity.md. Catalogs: an "Axis Angle"
row in every language.
Ellipse Properties in the Transform panel and the Properties panel's
Transform section now has a Constrain Pie Angle link beside Pie Start and
Pie End Angle. While it is on, a typed angle moves the other angle by the
same amount, so the pie keeps its size, as the help page describes:
https://helpx.adobe.com/illustrator/desktop/draw-shapes-and-paths/modify-live-shapes/live-shape-properties.html
- object.setLiveShape takes constrainPie with one of pieStart and pieEnd.
Every selected ellipse keeps its own span in one undo step; an angle
equal to the current one records none. constrainPie with both angles,
with neither, or with invertPie is a parameter error.
- VectorCraft's own rules: the link is off at every launch and is not
saved; the two panels share it; the span is counted counterclockwise
from the start angle to the end angle, across 0 degrees; a whole ellipse
stays whole; after Invert Pie the swapped span is kept; the on-canvas
pie widgets still move one angle at a time.
Docs: docs/mcp.md, docs/target-app-parity.md.
object.setLiveShape reports no change when the rounded ends stay where they
are. The Line Length and Line Angle fields send every edited value in one
call, so a length committed in the same frame as an angle step is applied.
A line drawn with the Line Segment tool now shows Line Properties in the
Transform panel and the Properties panel's Transform section, with the two
properties the help page lists for a line:
https://helpx.adobe.com/illustrator/desktop/draw-shapes-and-paths/modify-live-shapes/live-shape-properties.html
- object.setLiveShape takes lineLength (pt, above 0) and lineAngle
(degrees, brought into 0 to 360). Every selected line changes in one
undo step; a value that changes nothing records none.
- VectorCraft's own rules: the angle runs counterclockwise from 3 o'clock,
as the Rotate field does; a new length keeps the first end in place and
a new angle turns the line about its midpoint; a line whose ends meet
reads 0 degrees; the section shows only while every selected object is a
live line; a line that would reach past the coordinate limit is an error
that changes no line.
Docs: docs/mcp.md, docs/target-app-parity.md.
object.setBounds and guide.move move direct-selected anchors through the
same path as object.move, so they already followed the Interpolate
Control Points preference. They now list `interpolate` in their params
text and reject a value that is not true or false, also when the change
only scales the anchors or only guides are selected. A test covers both
commands with the preference on and off and with the param.
Faces and edges are the group's paths named Face or Edge, so type or a
group drawn in an isolated Live Paint group under one of those names is
no longer counted by Gap Options, Info or Make, and Expand keeps it, as
it keeps type named like the sources group.
Exit Isolation Mode while editing a pattern, an opacity mask or a symbol
applies a shape still being drawn with Real-time Drawing and Editing off
before the paths drawn in an isolated Live Paint group join it.
Leaving isolation mode in a Live Paint group (object.exitIsolation, or
object.isolate on a level outside the group) adds the shown, unlocked
paths, compound paths and groups of them drawn in it to the group as
Live Paint > Merge does, in one undo step. Faces and edges the new paths
do not cross keep their paint. This also applies when a group drawn in
the Live Paint group was isolated in turn. An exit with nothing to add
changes nothing and records no undo step.
Type, images, and hidden or locked objects drawn in the group, and
groups holding one, stay in it as they are. Gap Options, Merge and
Release now keep them; before, they replaced every child of the group
with the rebuilt parts, so such objects were deleted. Only the group's
sources group and paths named Face or Edge count as its parts.
Help page: https://helpx.adobe.com/illustrator/desktop/paint-and-fill/learn-painting-basics/modify-live-paint-groups.html
An Intertwine group's row in the Layers panel now takes dragged rows and
selected art inside it, as a group's row does, and an object dropped
beside one of its members joins the group too. The new member has no
arranged areas and is drawn in its row's order; the other members keep
theirs. Alt-drag adds copies. layer.move and node.move refuse an object
that is or holds an Intertwine group, a Repeat, a graph or a Live Paint
group with the reason Make gives. For such an object the panel shows no
inside box on the group's row and no drop line beside a member's row.
A member moved out of the group, by a drag, node.move or Send to Current
Layer, drops its arranged areas. A group left with one member is
replaced by that member, or becomes a plain group of it when the group
has an opacity, blending, appearance, mask, lock or hidden state of its
own; a group left with none is removed. Each move is one undo step.
With Use Preview Bounds on, Align, Distribute, Distribute Spacing, the
Transform panel and the bounding box measured a 3D object by its flat
source path, so the drawn surface stuck out past the box and aligned
edges did not touch. They now measure the projected vector art the
renderer draws, built with the document's symbols as the renderer builds
it: effects on single fills and strokes, group and symbol members, a
symbol instance with its own 3D effect, appearance overrides on dynamic
symbols, and geometry effects after the 3D effect. An instance with its
own 3D effect counts toward the 4,096-instance limit. Raster effects are
still not measured, and with the preference off the geometric bounds
are unchanged.
Docs: params text of object.align, object.distribute and
object.distributeSpacing, docs/mcp.md, docs/target-app-parity.md.
The new General preference Interpolate Control Points When Moving
Anchors (`interpolateControlPoints`, off by default) is the default of a
new `interpolate` param of path.moveAnchors (a Direct Selection drag),
object.nudge (the arrow keys), object.move, object.transform and
object.transformAgain. With it on, a move of direct-selected anchors
re-maps both handles of each segment with one moved end by the turn,
uniform scale and move that take the segment's old ends to its new
ends, so a segment between two corner anchors keeps its shape relative
to its ends.
- A segment with both ends moved, or with its ends at the same place
before or after the move, moves as it does with the preference off.
Only an exact move re-maps handles; any other transform of the anchors
is applied as before.
- A smooth anchor keeps its handles in line: its re-mapped handle takes
the new length and stays in line with the other handle, and when both
of its handles were re-mapped they point along the mean of their
directions. When the two point the same way, both move with the
anchor as with the preference off.
- The value used joins the command's journal entry and Transform
Again's options, so a replay or a repeat re-maps the handles alike
whatever the preference is then. A non-boolean value is an error.
- A retracted handle stays retracted, each drag or nudge is one undo
step, and a nudge of 0 still records none. Align and Distribute, and
the anchors of type paths and area type frames, move as before.
With the preference off, moves give the same result as before. The
label has a row in every catalog. The hook in transform_anchors follows
the patch bentschener attached to #7832; the handle math differs.
Fixes#7832
Docs: docs/mcp.md, docs/target-app-parity.md.
Co-authored-by: bentschener <353895224+bentschener@users.noreply.github.com>
- An instance of a pixel-aligned symbol on another symbol's editing layer is part of
that symbol's art, so it is no longer snapped and written into that art.
- Turning Align to Pixel Grid on for the symbol being edited now writes its art back
and shows it snapped on the editing layer at once, instead of after the next edit.
While a pixel-aligned symbol was open in symbol editing mode, every edit snapped its
art and walked the whole document for its instances, even when the art did not change.
That pass now runs when editing mode for the symbol ends; edits that change the art
still snap it and its instances.
Snapping an instance of a pixel-aligned symbol to whole points set its transform
directly, so the art of a linked opacity mask stayed at the old fractional position
and shifted against the artwork. The instance now moves as any move moves it, and
the art of an unlinked mask stays where it is.
symbol.new and symbol.options take alignToPixelGrid (off by default),
symbol.list rows report it, and the New Symbol and Symbol Options dialogs
show the checkbox. When it is on, the horizontal and vertical straight
segments of the paths in the symbol's art, opacity mask art included,
snap to whole points (half points for an odd centered stroke) at the
symbol's natural size, and its stroke weights become whole points. Each
instance placed at that size, reflected across one axis or not, moves to
whole points and goes back to them after every move. A scaled, rotated or
sheared instance, and an instance in another symbol's art, stays where it
is. In symbol editing mode the stored art and the editing layer snap
after each edit.
Duplicate Symbol, rename, copy and paste and symbol libraries keep the
setting, and Delete Symbol removes it.
Docs: docs/mcp.md, docs/ui-parity.md.
object.distribute uses spacing with a key anchor, and to: "selection" or
"artboard" makes the key anchor an ordinary point. docs/mcp.md and the
object.distribute and object.distributeSpacing params text still said
both commands ignore to and spacing with anchor points selected.
With Direct Selection, the point a Shift-click adds to two or more
selected anchor points is the key anchor. It is drawn as a larger filled
square in a frame, and the Align panel and the Control bar show the key
choice chosen as Align to Key Anchor. The Align buttons move the other
points to its x or y, and Distribute with a spacing places them from it.
A plain click still selects one point alone.
select.key takes {id, anchor} to set it, select.key {} cancels it, and
document.inspect reports it as keyAnchor. It goes when it is deselected,
deleted or left as the only selected point.
Pattern Options gets the Move Tile with Art checkbox under Size Tile to
Art. With it on, a move of all of the tile art in pattern editing mode
moves the tile as far as the art moved, pixel-grid snapping included:
object.move, object.nudge, object.transform with a translation, and
drags with the Selection tool. A group counts as moved when each of its
members moved. A move of only
some of the art, a copy, a rotation, a scale and a move of
direct-selected anchors leave the tile where it is. The option is off
for a new pattern.
pattern.options takes moveTileWithArt and pattern.list reports it. A
pattern.options call that changes nothing no longer records an undo
step.
An action or journal entry recorded before Scale and Reflect followed the
turned bounding box has no basis value. Replayed, such a step now acts along
the page's axes, as it did when it was recorded; steps recorded now carry
basis "box" and replay along the box. The built-in Reflect Horizontal action
names basis "box", so it keeps reflecting across the box's own axis.
The symbol test that reflects a turned instance names basis "page", which
is the reflection it was written for.
Since #7294, object.setLiveShape refuses a negative `radius` and a
`sides` that is not a whole number from 3 to 1000. Session::replay
applied the same checks, so a journal entry or action step recorded
before that change with such a value stopped with a parameter error.
On replay, a negative radius now counts as 0, which is how it drew
before. A whole side count below 3 or above 1000 is brought into that
range, and a fractional or negative one is ignored. Direct calls still
refuse these values.
A graph drew its axis lines and tick marks in 0.5 pt black and a radar
graph's rings in 0.25 pt gray every time, with nothing stored for them. A
stroke, fill, weight, recolor, Appearance row, graphic style, Eyedropper
pick or opacity given to them was lost when the graph was drawn again.
- The graph now stores the rows of its axis lines and tick marks
(axisRows) and, separately, of a radar graph's rings (ringRows): the
paint, weight, opacity and blend mode of the topmost visible fill and
stroke row, their order, and the line's object opacity and blend mode.
Every line of the kind is drawn with them. Dashes, caps, joins and
arrowheads are not stored.
- These commands store a line's rows: paint.setFill, paint.setStroke,
the stroke, gradient and recolor commands, paint.swap, paint.default,
Apply Fill to Stroke and Stroke to Fill, the appearance commands with
the Eyedropper, graphic styles, transparency.set and object.setProps.
paint.setFill, paint.setStroke and the recolor commands given a whole
graph now also store what they give its lines.
- When one command reaches several lines of a kind, the frontmost line in
paint order sets what the kind keeps. A gradient is stored without its
placement.
- Lines that show their default stroke store nothing, and a global swatch
edit or a document color conversion reaches the stored paint.
Docs: docs/mcp.md, the params text of these commands,
docs/target-app-parity.md.
transparency.set and object.setProps with isolate, knockout or
knockoutShape on a series group now store them for the series
(groupIsolate, groupKnockout, groupKnockoutShape), and the series group
has them again when the graph is drawn again. Randomize Opacity, Sort
Objects and Global Edit store the opacity they give a series group, so
a redraw no longer puts back an older stored value over it.
A move or copy of an appearance onto a series group whose stored values
differ from its own now counts as a change, so the edit is kept. Tests
cover graphicStyle.redefine of a style linked to a series group.
transparency.set and object.setProps with an object opacity or blend mode,
given a series group picked with Group Selection, set the group's own
opacity and blend mode, and the graph drew its series groups again
without them. The graph now stores them for the series (groupOpacity and
groupBlend) and puts them back on the series group when it is drawn
again. Commands that clear the group's own opacity and blend mode
(appearance.clear, graphicStyle.apply, appearance.transfer onto the
group, graphicStyle.redefine of a linked group) remove what the graph
stores.
object.setLiveShape was in params::UNCHECKED, so a key it does not read,
such as `path`, ran the command with the key ignored. Its description
names every key it reads, so it now goes through check_keys like other
commands, for MCP, scripts and command.batch steps. Each of `items` takes
`id` and `corners` alone; another key is refused as
`items[0].corner`, with the nearest accepted key. Saved steps still
replay leniently.
A `sides` that is not a whole number from 3 to 1000 (2.5, -1, 2, 1001)
and a negative `radius` are now errors naming the key, and leave the
document and its undo history as they were; a radius of 0 still
removes rounding. The Transform panel's Sides field takes 3 to 1000,
the Corners dialog's radius field stops at 0, and the panels' corner
radius fields send 0 for a negative value typed in.