The transform tool runs move, rotate, scale, reflect and shear as separate
commands. A shear angle that object.shear refuses, such as 90, a reflect
axis other than vertical or horizontal, or a scale of 0 failed only after
the earlier steps had changed the art and recorded undo steps. The tool now
checks those params first with the rules the commands use
(scale_factors, reflect_axis and shear_tangent, shared with object.scale,
object.reflect and object.shear), so a refused request changes nothing and
records no undo step.
find_command searched the list of about 1,000 built-in command specs in
order on every call, and a top-level command looks its id up at least
three times before it runs. It now finds a built-in in a map from id to
spec that is made on the first call. When an id is listed twice, the
map keeps the first spec, which is the one the search returned. An id
that is not a built-in still goes to the installed plug-ins' commands
at the time of the call, so installing or removing a plug-in shows at
once and built-ins keep precedence.
type.retype turns selected outlined text back into live point text when
each glyph shape is exactly a glyph of a loaded font, a font the document
uses or a family named in fonts: the same up to uniform scale, rotation
and translation. Matched glyphs map back to characters through the cmap
and become point text in that font and size at the same baseline and
turn, one object per line, with the first glyph's fill and stroke, in one
undo step. Shapes that match no font stay and are reported.
Matching (vectorcraft_text::retype) samples each contour at equal steps of
arc length and fits a similarity transform; it is bounded (faces, glyphs,
path elements, contours) and panic-free. Near matches, the ranked font
list, installed fonts not yet loaded and images are phase 2.
Undo and redo put back the whole document a step stored, so settings
that change without an undo step went back with it. Undoing any
earlier edit turned the perspective grid's Lock Grid off again, turned
its Snap to Grid back on, showed a hidden grid and switched the active
plane back. It also reset the grid from Gridline every and
Subdivisions, the export settings assets.settings.set stores, and the
current brush and symbol.
Each undo step now also records these settings as the step left them.
Undo and redo compare that record with the document they bring back:
a setting the step did not change stays as it is now, and a setting
the step changed comes back with the step. So undoing a perspective
grid preset still hides the grid the preset showed, and undoing a grid
definition that locked the grid unlocks it. The point Automatic Plane
Positioning holds still follows the steps, and is let go when the
active plane kept is another one.
`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.
Fold Preview (Object › Plug-ins › Packaging Tools, and the Fold Lines panel's button) shows the
document's blank folded about its largest panel, or the panel double-clicked. Creases and
perforations fold 90° away from the printed side and partial cuts 90° toward it. Each panel
samples a raster of the print, with the fold lines and non-printing layers left out, through its
projective map, with a depth buffer; the back shows the board's inside color. The window has a
Fold slider, seven view presets, orbit, zoom, pan and perspective, and its status line reports a
joint that does not close and panels that pass through each other.
- addon.packaging.fold returns each panel's frame, the hinges with their angle and gap, and the
collisions. A closing hinge's gap is measured with every hinge folded all the way.
- ui.foldPreview sets the window and rejects values of the wrong kind or out of range; saved
settings out of range are brought into range.
- The print renders off the UI thread where a worker exists and once per document revision. The
fold and the view image are worked out again only when the document, the settings or the
window's size change.
Unite, Minus Front, Intersect, Exclude and Minus Back close open paths,
so a straight line encloses no area and does not change the result.
Until now the line was dropped with no message. Reported in #7849.
- The reply of object.pathfinder.unite, minusFront, intersect, exclude
and minusBack now carries a warning, which the status bar shows, when
a selected object is or holds an open path that encloses no area once
closed (a line in a group or compound path included). The message
names Object › Path › Outline Stroke. The area is measured with the
path's fill rule, as Make Compound Shape's check in #7894 does.
- When such a path is what leaves the result empty (Intersect, or a
line at the back in Minus Front), the error says so. Objects that
leave nothing without the line keep the plain error.
- Both messages have rows in each complete-message catalog. The params
text and docs/mcp.md describe the reply field.
The Symbols panel and its panel menu asked for the current symbol on
every frame by running symbol.list, which builds a row per symbol and
walks the whole document once per symbol to count its instances. They
now read it from the active document with cmd::current_symbol, the
rule symbol.list itself uses for its `current`: the stored name while
a symbol has it, else the first symbol. symbol.sortByName,
symbol.place, symbol.options and text.insertInline use the same
function, and symbol.list's reply is unchanged.
An idle frame of the panel or its menu now runs no command, so on
macOS the native menu is not brought up to date on every frame while
the panel is open. In a document with 200 symbols and 50,000 objects
the read takes 0.035 us instead of 48.5 ms in a release build (thread
CPU time on Linux, median of 7 runs). The gain matters on large
documents; on small ones it is too small to notice.
Hovering with the Trim at Crossings Tool draws in red the stretch a click
there would remove, on the same paths and by the same rules as the click,
and nothing over empty canvas or hidden and locked paths. A drag draws
every stretch its rectangle or freehand line would remove while it
reaches at most 32 paths. In isolation mode only paths inside the
isolated object are highlighted.
What a pick removes moves from the command into
vectorcraft_tools::addons::trim::plan, which the command and the tool
both use. A preview spends at most a twentieth of the crossing work a
click may (Work::share); past that it shows nothing, and the click or
release still removes what it reaches. The tool keeps the crossings it
found for the document as it is, so moving along one path does not
search again, and kept crossings still count against a pick's work
budget. Work::spent_since and Work::draw in vectorcraft-pathops measure
and charge that work.
Docs: docs/mcp.md, docs/ui-parity.md, docs/target-app-parity.md.
A compound shape closes the open paths in it, so a straight line
encloses no area and contributes no area to the shape. Make Compound
Shape (and Alt-clicking a Shape Mode) still makes the shape as before,
and now returns a warning, shown in the status bar, when a member is or
holds an open path that encloses no area once closed, a line inside a
group or a compound path included. The warning names Object › Path ›
Outline Stroke. A self-crossing open path is measured by its fill rule,
so a bow tie whose signed area is zero gives no warning.
The warning has a row in each complete-message catalog.
Reported in #7849.
Port main's new variable-library parsing (variable kinds, image, visibility
and graph values) from roxmltree to craft-xml with the branch's strict
options and attribute validation. Keep both sides' variable tests.
Drop the stale docx::nesting doc link.
The Variables panel drew each variable as one "name · object" line in
the order the variables were defined, with no headers and no sorting.
The list now has three columns with headers: the type icon, Variables
and Objects. A click on a header sorts the list by that column, and a
second click reverses the order. The new command variable.sort {by:
name|object|type|none, descending?} sets the order, which is panel
state: not saved and not an undo step. variable.list lists the
variables in that order and reports it as sort. An unknown by, or a
descending that is not true or false, is an error.
dataset.import refused every header cell that starts with % unless it was
a variable's exact name, so the five-column example on the data source
set-up page did not import. A %Name header now defines the graph variable
Name, or names it when the document has it, and each cell of the column is
the path of a graph data file. The file is read as the Graph Data window's
Import Data reads one, and the data becomes the data set's graph value,
which applies as graph.setData applies it.
A relative path is taken from the new base parameter, else from the folder
of the CSV file at path. A file that is missing, can't be read or is larger
than 1 MB, a file that gives a graph value longer than 256 KB, and %
columns that hold more than 256 MB in all refuse the import with the line
and the column, and the document is left as it was. Each file is read once
per import.
Import Data's text decoding, cell splitting and sheet-to-data steps move
from the Graph Data dialog to the engine (graph/data.rs), so both imports
read a file the same way. dataset.export's warning now lists a % header
over values as refused and a %-prefixed variable of another kind as read
back with another kind.