In a window narrower than 352 points, messages narrow to the window's
width less the stack's margins, with 32 points as the least, and the
text wraps to that width. A message the app queues with Session::toast
shows for 0.5 to 60 seconds, as app.toast allows; a time that is not
a number shows for 4 seconds.
- The success level takes a new `success` theme token (the same green)
instead of the 3D axis color.
- docs/mcp.md names the plug-in conditions for `vc_call`, says no step is
recorded while a drag or typing is in progress, says a failed script run
keeps the messages it raised, and names the headless MCP server and
`vectorcraft-cli run` as the sessions without a window. Lines wrap like
the rest of the file.
- The params text and the error say "whitespace", which is what the check
rejects.
- A new test runs a script that draws, raises a message and throws: the
drawing is put back and the message is kept.
- The long-message test also checks that the stack stays inside the
window.
- The evidence line in docs/target-app-parity.md moves after the Scripts
entries.
The click took the frame's automatic id, which follows its position among
the messages, so a message pressed while an older one expired did not
close on release. The click now takes an id from the message's own scope.
`app.toast {message, level?, seconds?}` queues a short message that the
desktop app shows at the window's bottom right. It closes after its time
(4 seconds by default, 0.5 to 60) or when clicked. At most 5 show at
once, the newest lowest; a message shows at most 6 lines with the whole
text on hover, and a stack taller than the window scrolls. `level`
(info, success, warning, error) sets the color of its edge.
Scripts raise one with `vc.run`, MCP clients and plug-ins through the
command, and an action records it as a step. The app's own code calls
`Session::toast`. The command edits no document and adds no undo step;
invalid values are errors. Part of #7523: the tick sound is not
included.
Docs: docs/mcp.md, the Automation evidence in 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.