The Transform panel measured the selected objects' Align to Pixel Grid state on every frame, looking up each object and its parent and collecting their ids. With Select All in a large document that cost tens of milliseconds a frame. The state (on, off or mixed, and whether every object can be aligned) is now kept in the canvas cache for the document's uid and revision, and the ids are listed only when the box is clicked.
Follows #7608. Text from EMF, WMF and EMF+ pictures was laid out with the
font's own spacing, so the per-character advances the file gives
(ExtTextOut's lpDx, EMF+ DrawDriverString glyph positions) were dropped.
- Characters are spaced by their advances as tracking, with pair kerning
off. When a ligature forms at one tracking and breaks at the next,
standard ligatures are turned off for that text.
- On a single left to right line, an advance that tracking can't give
(wider than its range, or a tab) starts a new point type object where
the advance puts it, also between the letters of a ligature the
tracking breaks apart. An underline or strikethrough is filled across
the space between. Right to left and multi-line text stays one object.
ExtTextOut: https://learn.microsoft.com/en-us/windows/win32/api/wingdi/nf-wingdi-exttextoutw
DrawDriverString: https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-emfplus/b794b780-e9a8-4682-af65-9b614aecfbe6
With Rectangle, Rounded Rectangle, Ellipse, Polygon or Star active, a
double-click on a visible corner widget of a selected live rectangle or
polygon shows and selects the Transform panel (window.panel.activate),
wherever it is: closed, docked behind another tab, floating, in an icon
column or in a dock hidden by Tab. A second double-click keeps it on show.
The tool, the selection, the document and the undo history stay as they
were. Pie widgets, spots off the widgets, Line Segment, plain paths and
hidden or angle-excluded widgets do nothing; the Selection and Direct
Selection tools keep their double-click behavior.
Tools return the new Action::Panel, which the engine forwards as
UiRequest::Panel; the desktop app activates the panel, and a headless
pointer_gesture reply carries {"panel": id} in its requests.
Docs: docs/ui-parity.md (#5477 row, also correcting its statement that the
bounding-box handles scale only with the Selection tool) and
docs/target-app-parity.md.
While Alt (Option on macOS) is held, the dialog's Cancel button reads
Reset. Reset puts the remembered settings back, or the defaults when none
are remembered, on the current document's active artboard. It drops a
pending preset, a pending Done left by a Done that failed, the preset name
being typed and the selected color table entry, and keeps the view, zoom,
connection speed and path. It does not remember or write anything, and the
dialog stays open. `ui.dialogReset` does the same.
The line under the Preferences fields now shows a sentence for each of
the 23 Type settings when the pointer is over the setting's row or its
control has the keyboard focus, and a screen reader gets the same
sentence. Each sentence states what the app does with the setting, such
as which keys step by each increment and which panels show the East
Asian and Indic options. Every complete catalog has a row for each
sentence.
The empty-line test now points at Guides & Grid › Gridline every, a row
that still has no sentence.
With the Flare tool, an Alt-click (Option-click on macOS) now draws a flare
centered at the click at once, with the tool's current options, instead of
opening the Flare Tool Options. Alt counts when it is held as the button goes
down; a drag with Alt draws the flare in two stages as before. While the
perspective grid shows with an active plane, the flare is drawn on that plane
from the click, as the dialog's OK draws it, and a click the plane cannot take
reports the error. A plain click still opens the dialog.
When a threaded frame starts inside a numbered paragraph, restartNumbering
false on that frame no longer takes away the number the paragraph has in
the frame before.
The line under the Preferences fields now shows a sentence for each of
the 14 Selection & Anchor Display settings when the pointer is over the
setting's row or its control has the keyboard focus, and screen readers
get the same sentence as the focused control's description. Each
sentence states what the app does with the setting: the Snap to Point
sentence says that the Smart Guides Snapping Tolerance applies while
Smart Guides is on. Every catalog has a row for each sentence.
The test that every General setting has one sentence now covers
Selection & Anchor Display too, and two more check the line on hover
and on keyboard focus in that category.
While the Type tool edits text, the Properties panel's Character section
showed the font family and style of the text object's first run. It now
reads character::text_style, as the Character panel, the Control bar and
the Contextual Task Bar do: the first selected character's style, or the
style of the character before the caret. With the Selection tool it still
shows the first run's.
Fixes#8189.
A trim checked and changed the selection once for every trimmed path
and every piece, and each check or removal went through all selected
objects, so a trim of thousands of selected paths spent time
quadratic in their number on the selection alone. The command now
reads the selection through a set and removes and adds objects once
at the end. The resulting selection is the same as before, including
object order, the key object and key anchor, the direct-selected
anchors and segments, and the fields that a change to the object
selection clears.
The crossing search took a crossing only where the straight pieces it
splits two curves into actually cross. A line trimmed at a curve ends
where that search found the crossing, up to about 0.0001 pt off the
curve. Once the curve was cut as well, its segments were split
differently, the line's end could fall just short of them, and the end
no longer counted as a place on the curve. Trim at Crossings then
removed the curve past that line, to the next crossing or the whole
path.
An open end of a path that lies within 0.001 pt of another path now
meets it at the nearest point there, at any angle. Corners of a path
and closed paths keep the exact test, and paths that lie along each
other still don't cross. Trim at Crossings and its hover, Add Points
at Crossings (with and without cut) and the Join tool's trim and join
of crossing paths use this search. The params text of Trim at
Crossings and Add Points at Crossings and docs/mcp.md say so.
When a threaded frame starts inside a numbered paragraph, startNumber and
restartNumbering true now go to the next numbered paragraph that begins in
that frame. Before, the continued paragraph took the number, and reflow gave
it to the item the earlier frame shows.