A TJ can draw the same glyph at the same place twice (its kerning goes
back), so a stroke can't be matched to a filled glyph as it arrives:
[(A) -3500 (B) 4834 (A)] TJ put the first A's stroke on the last A and
left the earlier parts unstroked. Strokes over filled glyphs are now
held until their stroke pass ends and then matched to the glyphs filled
last, in the order they were filled, so each copy is stroked where it
was filled, while a glyph filled and stroked where one filled before
stands still strokes only the newest. At most 4096 strokes are held.
Docs: ordinary text gives one filled and stroked object per part; in an
ActualText span it stays one replacement object on the first glyph's
line and style.
The reader fills every glyph of a text-showing operator, then strokes
them. When a TJ's kerning started a new line part way through, the
first line was finished before the stroke pass came back to it, so its
strokes found no filled glyph and came in as stroke-only type over
fill-only type.
A line a glyph doesn't fit is now parked while a stroke may still be
drawn over it, and a stroke-only glyph is matched against the open line
and then the parked lines, newest first. Parked lines are finished
oldest first before the open line, so drawing order is kept, and at
most 64 are parked.
When every shape is left out because it would have no size, for example
Add Bounding Rectangle on a straight horizontal line, the error is now
"the shape would have no size" instead of "nothing to enclose", which
stays for objects with no outline. A shape that would reach more than
4,000,000 pt from the origin, for example with a very large `offset`,
is refused with "the shape would reach past the edge of the canvas"
before anything is drawn. Both messages are in the 24 catalogs that
translate messages.
The params text of addon.pathtools.boundingCircle now names the
sublayer rules that docs/mcp.md states: sublayers that clip their
contents count by their clipping paths, other sublayers by their shown
objects. Both commands' params text lists the errors.
The menu items open no dialog and draw one shape around the whole
selection with no offset. docs/ui-parity.md, docs/target-app-parity.md,
docs/mcp.md and the ROADMAP line now say so, and name `each` and
`offset` as command parameters only.
New tests: the menu items in vectorcraft-ui-egui, the canvas-edge error
in vectorcraft-engine, and shapes::convex_hull in vectorcraft-geom.
After a click, the circle the tool drew is selected and on top, so the
next hover or click near the point it touches snapped to that circle
instead of the path. The pointer now passes over the circles the tool
drew until an edit, Undo or Redo is made outside the tool.
- An anchor marked smooth is a corner when its handles turn by 90° or
more; the params text and docs/mcp.md now say so instead of "turn
back the way they came".
- Tests cover a second click after a draw, in the tool and through the
session, and a marked-smooth anchor with square handles.
The writer passed no language to craft-pdf, so exported and printed
PDFs had no /Lang and accessibility checkers failed primary-language.
Writer::new now passes the BCP 47 tag of the Document Setup language
(new vectorcraft_doc::setup::language_tag, en-US by default) through
write::Writer::new_with_language, which writes the catalog's /Lang and
the XMP dc:language. A language with no tag writes none. /MarkInfo is
left for tagged PDF (#3643).
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.
- `Unit::parse` keeps main's paragraph about units after `*` and `/` as it
was; the new `x` paragraph follows it, and the limit line names the
signs it counts again.
- `object.path.offsetPath` takes `"0.05x2 in"` (0.1 in), which it refused
before; `"0x10"` reads as 0 pt. docs/mcp.md states both.
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.
Align to Selection, Align to Key Object and Align to Artboard follow the
align items in Object › Align, with the choice the Align panel shows
checked. Each is a UI command (align.toSelection, align.toKeyObject,
align.toArtboard) that sets the choice as the panel's Align To button
does, and Edit › Keyboard Shortcuts lists them under Align with no
default key. align.toKeyObject fails with "no key object" when no
object can be made the key.
- A canceled press on the second segment (a canceled touch, a second
finger) draws nothing and leaves the first segment picked. A canceled
press that picked the first segment leaves no segment picked. Before
this change a canceled press worked as Escape and forgot the first
segment.
- Shift pressed or let go during a click on the second segment, before
the pointer moves far enough to start a drag, counts at the release:
the circle is looked for again with or without the tool's radius.
- A session test sends the tool's release with a command that fails and
checks that the first segment stays picked.
- The radius option's test checks that a value outside 0.01 to 1000000,
or one that is not a number, leaves the radius as it is.
Docs: docs/target-app-parity.md lists every kind of circle the tool
leaves out: circles whose nearest point on the second segments is not on
the circle, circles that cross the first segment, circles that touch
both segments at one point, circles without a finite radius above 0, and
circles too small or too large for three of their points to give them
back. A circle found twice is kept once. docs/mcp.md says that in a
drag the circle touching nearest the press is drawn, and that the
radius option is not checked yet.
Part of #7178.
A marquee across the shapes that the geometry effects of a symbol
instance's active fill or stroke paint outside its box now selects the
instance, as a click there does. An image is likewise touched where its
own fills and strokes paint outside its frame. Outline mode keeps the
box alone.