The transform tool treats a null reflect, copy or origin, and a null
numeric step, as given, but its inputSchema allowed only the non-null
types, so a client that validates against the schema could not send
them. Each of those properties now also allows null. The transform row
in docs/mcp.md says a step that is neither a number nor null is an
error, and that a null dx or dy counts as 0 and still runs the move.
With no place to go on from, the dialog left out edit.findNext's from, so the search went on after the selected type object and passed over its matches: after Find selected a type object, changing the Find text skipped the matches in it. edit.findNext now starts at the first match for a null from, and the dialog sends one.
recolor.apply with `group` rewrote the group by place: the new colors went
to its swatches in order, so a gradient, pattern or None swatch in the group
took a color or was removed, at OK and in the live preview.
The group's colors, from the rows or from `groupColors`, now go to its color
swatches in order, and every other swatch keeps its place and its paint.
`groupColors` counts the color swatches only, as the dialog already does
when it lists a group's colors. swatch.editGroup is unchanged.
`transform` read `reflect` with `as_str`, `copy` with `as_bool` and
passed `origin` through unchecked. A `reflect` of `42` or `true`
skipped the reflect step and reported success for the steps before it,
a `copy` of `"yes"` transformed the original instead of a copy, and an
`origin` that was not two numbers fell back to the selection centre.
The handler now checks all three before it selects `ids` or runs a
step, and returns an error that names the argument. A null value of
any of the three is left out. The tool description and the
`transform` row in docs/mcp.md say so.
Fixes#6448
A point counts as on the path's outline when it is less than the
touching tolerance from it, with its distance from the path's center in
place of the distance between centers. The params text, docs/mcp.md and
the progress doc now say so, and say that every Tangents choice in the
dialog gives the same lines for a point.
Tests: a point half the tolerance inside and outside a circle gets the
one line there, and farther off gets none or two; a point placed on a
turned outline gets a line as long as the outline is wide along it; the
dialog previews the same two lines for every Tangents choice and keeps
them as one step, and a point inside changes nothing and says why.
ui.dialog.confirm used to read a replace that is not a string as empty text, so Replace All could delete every match, and a switch that is not true or false as off. It now returns the error, which shows under the match found, and runs nothing; the match stays for Replace once the field is set right.