graphicStyle.apply with add, and appearance.copyFrom with append, stored
both the fill and stroke rows a graph label or axis line showed, so a
fill-only style added to one axis line replaced the stroke the axis lines
kept from another line with the line's own black stroke. They now store
only the kinds of row they add; the row of the other kind keeps its paint
and its place relative to the characters as the kind keeps them.
appearance.moveItem of the Contents row stored the rows of every label
it was given, so a move that changed nothing on a label replaced what its
kind kept from another label. It now stores rows only for the labels
whose rows it changed.
paint.setFill, paint.setStroke, addon.color.fillToStroke and
addon.color.strokeToFill on an axis line, tick mark or radar ring that
already showed the paint they write stored nothing, so a paint its kind
kept from another line came back when the graph was drawn again. The
paint written to the line's topmost visible fill or stroke row is now
stored for its kind; its other attributes stay as the kind keeps them.
Takes #7375's later fixes: Move Appearance onto an axis line behind its
source, picks and added styles without transparency, Default Fill and
Stroke on an axis line, and edits that keep only the line attributes they
change. Aligned row edits, hidden rows, reorders and Default Fill and
Stroke on labels keep this branch's behavior.
A no-op appearance.moveItem on a graph axis line or label replaced the
rows its kind keeps with the line's own. The reorder now keeps rows only
for the lines and labels whose rows it changed.
text.setStyle keeps the default label style for a kind only when the
command gives a character attribute; justify-only and empty
featureChanges requests record nothing.
Default Fill and Stroke on an axis line, tick mark or radar ring that already
shows the default paint now stores the default fill and stroke rows for every
line of its kind, so a stroke the kind kept from another line no longer comes
back when the graph is drawn again. The object opacity and blend mode the
kind keeps stay as they are.
A whole pick of every fill and stroke attribute, or an append pick, onto
a graph's axis line, tick mark or radar ring stored the line's rows in
full, object opacity and blend mode included, even when the pick did not
apply the object's transparency. On a line that still showed 100% until
the graph was drawn again, that replaced the opacity its kind kept (40%
set on another line became 100%). An append pick onto a graph label, and
graphicStyle.apply with add on a label or line, did the same.
Without Transparency applied, these picks, and a style added on top, now
store the fill and stroke rows and leave the kept object opacity and
blend mode as they were.
Move Appearance captured the cleared source and the targets together, and
graph lines are captured in paint order, so a source in front of its target
replaced the kept axis rows with its cleared ones. The targets are now
captured again after the source.
- A graph opened from a .ai file now saves `placedArt` too. Moving or
restyling one of its labels before the first redraw no longer moves or
stretches the plot.
- Type > Create Outlines on a graph's labels now adjusts the saved bounds,
so the outlines do not read as a move at the next redraw. A move of
the graph made before the outlining is still followed.
- A `placedArt` with no width or height falls back to the bounds of all
of the art, as a graph saved without it does.
- `art_bounds` moves to the doc crate so the .ai reader can use it.
- docs/mcp.md describes `placedArt`, `placed` and when a redraw follows
a move.
- Tests: a legend across the top, a legend after a right value axis and
legend labels of several lines keep the plot in place through label
size changes; moving a category label on its own; outlining labels
before and after a move; a flat `placedArt`; a label moved in an
opened .ai graph.
Only a pie with Legends in Wedges picks its legend labels' fill, white on
dark wedges. Paint visits and swatch mappings now leave its default black
legend fill out only for such a pie; other graphs draw the kept fill, so
it is visited and mapped like the other label fills. A color mode change
still leaves the default black legend fill as the default, so turning on
Legends in Wedges later keeps the white labels on dark wedges.
The next redraw of a graph compared the bounds of all its generated art,
labels included, with the bounds stored at the last generation, and took
any difference for a move or scale of the graph. Label edits that change
the size of the type (a new size, an indent, a legend size) changed those
bounds without a move, so the plot shifted and stretched when the graph
was drawn again.
The spec now also stores the bounds of the art without type
(`placedArt`), and moves and scales are measured on those. Graphs saved
without them are measured on the whole bounds as before. Moving one
label with Direct Selection no longer moves or stretches the plot at the
next redraw.
On a pie with Legends in Wedges, the graph draws legend labels white on
dark wedges unless they keep a fill of their own, and it read a kept black
fill as no fill of its own. A label recolored from white to black on a dark
wedge went back to white the next time the graph was drawn.
The graph now marks the legend labels' fill as set when a command sets it
(legendFillSet in the graph's label styles, kept through save and open), and
draws a marked fill on every wedge, black included. Undo clears the mark. A
size, font or stroke change does not set it, and neither does a whole-pie
recolor that gives the legend labels different fills; one that gives them
all the same fill sets it. A swatch edit or color conversion leaves the
default black legend fill as it is, and keeps a non-black legend fill from a
file saved without the mark as the labels' own when it turns black.
A pick of only overprint, caps, joins, miter limit or dashes on an axis
line or radar ring no longer stores the line's paint and weight for its
kind, since the graph keeps none of those options.
graphicStyle.new linked the object it was made from, the art of a column
or marker design in a graph series included, and graphicStyle.redefine
gave the new look to every object still linked to the style. Redefining
the style from another object then restyled that art, which the graph
draws again from the design.
- graphicStyle.new makes a style from the art without linking it.
- graphicStyle.redefine leaves the art's look as it was and unlinks it,
as an edited object is, whether the art is a linked object (as in a
document saved before this change) or the source.
Docs: docs/mcp.md, the params text of graphicStyle.new and
graphicStyle.redefine.
An edit that changed only some attributes of a graph line, such as a
transparency-only Eyedropper pick, a cap, or a fill, kept that line's whole
fill and stroke rows for every line of its kind. A line that still showed
the default stroke until the graph was drawn again then replaced the stroke
its kind kept from another line. Such edits now keep only the attributes they
change; Clear Appearance, Move Appearance, graphic styles, and a pick of every
attribute or with append still keep the whole rows.
An Appearance, paint, stroke or transparency edit of a hidden fill or
stroke row of a graph label or axis line no longer stores that object's
unchanged visible rows for its kind, so a paint the kind keeps from
another label or line stays.
An aligned appearance.setItem, removeItem or duplicateItem given the Axes
group stores the rows of only the lines and labels that have that row, so
a category label without it no longer replaces the rows its kind keeps.
An Eyedropper pick of only the object's transparency stores only the
opacity and blend mode of an axis line or radar ring, as transparency.set
does. Default Fill and Stroke stores the black fill and no stroke for a
label's kind, and the default rows for a line's kind, also when the label
or line already showed them; a kind that keeps no style and is left at the
default style still keeps none.
With apply "opacity", Sort Objects compared each object's opacity with the
value it gets as a percentage, within 1e-6. An evenly stepped value can
differ from a mark's percentage by more than that while it rounds to the
same stored opacity: marks at 30%, 65% and 100% sorted by x with
distribute on keep their opacities, yet the 65% mark counted as changed.
The sort then made an undo step and replaced the opacity the graph stores
for the series (30%) with 65%.
The sort now compares each object's stored opacity with the opacity it is
given, as stored, both to skip a run that changes nothing and to pick the
marks whose opacity the graph keeps.
A recolor that reached a pie's legend labels through the graph kept their
new fill as the legend's own when every label ended up with one color (a
one-series pie), so a wedge painted light again kept a white label.
Legend label fills on such a pie are now kept only when the edit named
the labels.
A paint write that leaves a series mark's gradient as the graph drew it
now keeps the series' stored gradient and its unit-box flag in two more
cases:
- a mark with no width or no height, such as a column for a value of 0,
where the stored gradient was replaced by the mark's gradient in
document coordinates and no mark took it on the next redraw;
- a gradient kept in document coordinates (a file saved before the unit
box), which a stroke weight written as it was moved to the unit box,
so the next redraw placed it on each mark's own box.
The appearance.* commands, graphicStyle.apply, graphicStyle.redefine,
graphicStyle.breakLink and transparency.set with an item, given a
graph's Axes group or Legend group, edited the group's own appearance
stack. The graph draws those groups again with no rows of their own,
so the next redraw (for example after graph.setData) removed the
edit.
These commands now read such a group as they read a series group: the
Axes group stands for the axis lines, tick marks, radar rings and
labels directly in it, and the Legend group for the legend labels. The
graph keeps what the command sets for every line and label of each
kind. graphicStyle.new and the other commands that read a look read
the topmost member of a group that holds nothing of its own. A group
with a fill or stroke row of its own, or with no line or label in it,
is still edited itself, except by graphicStyle.redefine, which passes
the style to the members of a linked group.
The lines and labels of a new graph have different rows, so a row
index given the Axes group would name a different row in each. An
index or item given such a group is now an error unless `aligned` is
true, which makes it a row of the backmost member's stack.
Docs: docs/mcp.md, params text, docs/target-app-parity.md Graphs line.
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.
The test now sets the edited label's gradient vector and aspect with paint.setGradientGeom and checks that the gradient is placed before the graph redraws, so the later check that the kept gradient has no placement fails if the redraw keeps it.