A diagonal Shift move that slides onto a ruler guide again checks an
artboard guide's run where the move put the bounds, not where the slide
would put them, so the guides a Shift move reaches are the same as on
main. A selection held by its edge still checks where the slide puts
the bounds. A test covers a diagonal Shift move whose middle is beyond
an artboard guide's end.
The Drawing aids line now names the Selection tool for edge holds and
says the slide does not go past the path's ends.
The PDF writer dates each file and makes its IDs from the clock, so two
sheet exports on either side of a second boundary differed there and the
test failed on main's coverage run.
Each <textPath> with an href walked the whole document to find the element it names, so a file with many texts on paths took time proportional to the number of texts times the number of elements. The importer now builds a map of element ids at the first such lookup, keeping the first element in document order for each id, and looks each href up there. Files whose texts name no element do not build the map. The imported document is the same: a test compares the whole document and warnings with the per-id walk, including duplicate, missing and unusable ids.
With Smart Guides on, a selection the Selection tool held by a point of
a path's edge (a press on its stroke, on its outline in Outline view, or
on the fill within 6 screen points of the edge) snapped that point only
to other anchors and centers, or lined its bounds up. It now also lands
on the other objects' paths ("path") and where paths and ruler guides
cross ("intersect"), as a selection grabbed by an anchor does since
On a straight path, the selection then slides along that path, the
point staying on it, until its bounds line up with other objects, are
spaced evenly with them or line up with a ruler guide. The slide goes
at most twice the Snapping Tolerance and not past the path's ends. On a
curved path and at a crossing the point lands as an anchor does, and
the bounds do not line up.
Clicking between app windows (floating panels and the canvas) passes through one frame where none of them has focus. The palette levels counted the app inactive on that frame and lowered every floating panel's OS window. The panels flickered, could end up disappearing behind the main window until the next repaint, and a click on one panel's bar could hand the keyboard to another.
The app now counts as inactive once none of its windows has had focus for 0.25 s, counted from the first frame that saw none. craft-ui's docking waits as long.
Fixes#6986
- The French script error line now has the catalog's no-break spaces before its colons.
- es.tsv drops the old file.info control character row a merge brought back.
Two PRs merged tonight each added the same row, so bundled_catalogs_are_consistent fails on main
(gu: duplicate "" "Panel"). Both rows have the same translation.