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.
`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.
Object › Transform › Rotate Bounding Box… asks for an angle and turns the
bounding box of the selected objects by it, leaving their art where it
is. Reset Bounding Box squares it again.
- object.rotateBoundingBox {angle, absolute?}: by default the box turns
by angle from the angle the selected objects share (0 when theirs
differ); absolute: true turns it to angle. Objects with different
angles get one shared angle, and the objects inside a group or a
linked opacity mask turn with it and keep their relative angle. A path
of a compound path selected on its own turns only its own box, the
same objects the transforms move. An angle within 1e-6° of 0 is
stored as 0. One undo step, none when every box is already at the
angle. A missing or non-numeric angle is an error. changed counts
every box that turned, as object.resetBoundingBox counts the boxes it
squares.
- object.resetBoundingBox squares only the box of a compound path's
path selected on its own, instead of the whole compound path.
- Menu labels in every catalog.
Docs: docs/mcp.md, docs/target-app-parity.md.
Part of #5954.
When two File objects held changes to the same file, copy, length, a
new open of the file and a withdrawn grant wrote them in no fixed
order, so the copy or the file could end up with the older object's
bytes. They now write them in the order the objects were opened, as
the end of the run does.
When Add to Swatches brought a library pattern whose art links to a global
or spot color, and the document had that name for another color, the
pattern was relinked to the document's color. Adding the library's color
then made a numbered copy that the pattern did not use. The color now comes
in under a numbered name and the pattern links to it, as an added color
does, and the check for a pattern already in the document compares it the
same way.