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.
A printer name in "Sent “{title}” to {to}" was translated as a message of
its own, so Korean's "{status} ({e})" row turned "Office Laser (Floor 2)"
into "Office Laser(Floor 2)". An unquoted `{to}` value is now translated
only by an exact row, such as "the default printer"; a quoted one stays
as written. The cross-language case uses a printer name with
parentheses, and two quoted `{to}` names that match exact rows.
Overrides::is_set is only called from main under cfg(not(macos)), so it is allowed to be unused there (the repo's cfg_attr pattern). settle_cut_edges walks blended with iter_mut().enumerate() instead of indexing it.
Look::takes let a glyph filled only join a run whose glyphs were also
stroked, so after mode 2 text a mode 0 glyph took the run's stroke:
`2 Tr (B) Tj 0 Tr (C) Tj` came in as "BC" stroked throughout. A glyph
now joins only a run drawn alike (fill, stroke, overprints), so a glyph
filled only starts a run of its own and takes a stroke only when the
matched-stroke path (#8039) strokes it.
flush_stroke no longer strokes a whole run in place: a whole run goes
through the split and join code, so fill and stroke rendering glyph by
glyph still builds one stroked run.
egui places a popup by its size the frame before, so on the frame a late-measured name widens the
menu the filter text can stay where it was while the menu's rect already reaches past the window.
The helper now waits until both the filter and the menu's rect stay put, which fixes the
intermittent failure of a_menu_wider_than_its_field_stays_in_the_window (the menu ending 0.7 pt
past the window's edge).
Type on a path sits at fractions of its path's length. Scaling the path
non-uniformly changes where a fraction lands (CodeRabbit's case: M0 0 L100 0
L100 100 under diag(2, 1) moves the start bracket from (200, 0) to (150, 0)).
Path type now bakes the vertical scale into the character sizes and scales
its path uniformly by it, which keeps every fraction where it was; the
horizontal stretch stays in the transform.
A Swatch Options rename of the spot color base keeps it the base, also
as a command.batch step, and so do an Undo and a Redo of the rename.
Deleting the swatch or its color group, merging it into another, making
it a process color or closing its document ends the link, so a later
spot color of the same name does not become the base until it is chosen
again. The base keeps the color it showed.
A batch's Activate Document, New, Open, Close and Move Document steps
are followed, so steps in another document leave the link alone. When
the swatch goes in a way the panel does not follow, the link waits for
an Undo or Redo, and the next other command ends it.
Baking an object's scale into the character attributes removed that scale
from the type's transform, but the area frame (and a path type's path), which
is drawn through that transform too, kept its unscaled size. A 120 x 80 frame
scaled 200% shrank back to 120 x 80 on the page, so the 24 pt type broke into
two lines and the rest became overset.
The frame and the path now take the scale the transform loses, so they, the
line breaks and every glyph stay where they were.
Fixes#8297
A PDF/X-4 export wrote xmp:ModifyDate and xmp:CreateDate in its XMP
metadata but no xmp:MetadataDate. The PDF/X-4 metadata edit now adds
xmp:MetadataDate next to xmp:ModifyDate, with the same value, and grows
the stream's /Length to match. When the export dates the file as modified
later, post::modification_date already rewrites every xmp:MetadataDate,
so the two dates stay equal.
PDF/X-1a, PDF/X-3, PDF/A and plain PDF exports are unchanged.