After a zoom step's preview the render thread only checked once, right away,
for a newer request, then started the full render. That render can't be
stopped, so on a heavy page every later step of a held zoom waited for it
(110-520 ms per render on a 9,000-layer page with images and shadows).
It now waits like the browser worker does: SETTLE_MS, or the last full
render's time when that's shorter. Pans and edits have no preview and are
refined straight away as before.
craft_fig_src() ran `cargo metadata --offline` with no platform filter.
Cargo then needs every target's packages in its cache, and a cache that
holds only what a host build fetched lacks iOS-only crates such as
accesskit_ios, so the nightly FreeBSD job failed. Ask the same cargo for
its host triple (`cargo -vV`) and pass it as `--filter-platform`.
* M9: page.setOpening sets the page a shared file opens on, for everyone who joins (#1817)
A file on a figcraft-server opened on the page current at publish time, with no way to change it:
`DocProp::CurrentPage` was synced but nothing wrote it (`page.select` is each viewer's own page,
only a local save stamps the document). `page.setOpening {id?}` writes `doc.current_page` as a
document edit: one undo step, a synced change in a live session, so every later join opens on it;
the current page when none is named; a divider or a layer refused; nobody's own page moves. The
pages list's context menu gets "Set as opening page". Docs: mcp.md, collaboration-parity.md.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
* M9: the pages menu's new string is in the English catalog (#1817)
The gate's i18n test wants every tr() key in locales/en.toml.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
* Opening page: the parity doc states the default when no opening page is set (#1972 issue)
With none set, a file opens on its saved current page, not the first page, and a link cannot name a page, so the row is partial.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
* Opening page: one sharing row, and the spotlight exception on the opening-page row (#1972 issue)
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
* Opening page: the parity row states where the joiner's page comes from (#1972 issue)
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
* Opening page: a no-op set adds no step, deleting the opening page falls back, and the tests cover junk ids, refusals, undo and the menu item (#1817)
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
* M5: the chosen opening page is saved with the file and opens it for everyone (#1817)
The opening-page flag now lives on the page node (NodeKind::Page opening), so it syncs
through the existing node kind. Saving writes the flagged page as current_page instead of
the page the saver was viewing. A duplicated page does not copy the flag, and deleting the
page removes it.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Model-Effort: Opus 5.5 drove; Opus 5.5 briefed; Sonnet 5.5 wrote at medium
---------
Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
On revert, fired-delay keys are kept only for layers the restored document has: a layer only the hover variant had is gone again, and its id may be issued anew by the next hover. Test a_hover_variants_own_layer_leaves_no_fired_key_after_the_revert (red before: a key for the missing NodeId(8) stayed); present 106 passed, clippy clean (CodeRabbit on #2362).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The body below the header had a 160-point floor, so with the minimum capped by a screen lower than 220 points the content ran past the window. It now takes the height left below the header (the table scrolls). Test on_a_short_screen_the_variables_window_fits_inside_it (red before: the window ran to y 206 on a 180-high screen); variables 45 passed, clippy clean (CodeRabbit on #2363).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A fired-delay key is (node, index), and inside an instance the index belongs to the variant shown. On revert, keys that fired during the temporary change inside an instance it changed the variant of are dropped (they name the hover variant's interactions); the snapshot's keys come back and the other new ones stay. Test a_delay_fired_on_a_hover_variant_does_not_block_the_restored_variants_delay (red before: A's runs left 0, right 1); present 105 passed, clippy clean (CodeRabbit on #2362).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The minimum (600 x 240) is capped at the screen less its margin, so on a screen narrower than that the window stays inside it. The window is pinned at its top-left corner and opens centred, so dragging one edge leaves the opposite one in place (the centre pivot moved both). Tests on_a_narrow_screen_the_variables_window_fits_inside_it (red before: the window ran from x -26 to 576 on a 550-wide screen) and the top-edge check in the_variables_window_grows_when_dragged_taller (red before: 210 -> 190); variables 44 passed, clippy clean (CodeRabbit on #2363).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The while-hovering / while-pressing snapshot also keeps the fired After delays, and the revert puts back the ones the temporary variant change cleared (keeping any that fired during it), so a delay that already ran on the variant doesn't run again. When an edit in the editor replaces the presented document, the run-time swap times are cleared with the rest of that state.
Tests: a_hover_variant_that_reverts_does_not_rerun_a_fired_delay (red before: count left 2, right 1) and an_edit_while_presenting_drops_the_swap_times (red before: left Some(0), right Some(1)); present 104 passed, clippy clean (CodeRabbit on #2362).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
At 480 points the table was 279 wide, leaving 11 points next to the 220-point search field for a library collection's Extend collection button. The minimum is now 600 x 240 (table 399 wide); the default size's clamp uses the same minimum. variables 43 passed, clippy clean (CodeRabbit on #2363).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The swap times now travel with the while-hovering / while-pressing snapshot, so reverting a hover's variant change restores them and the variant shown again fires on its own deadline. Test a_hover_variant_that_reverts_keeps_the_after_delay_deadline (red before: left Some(0), right Some(2) at 1.3 s); present 102 passed, clippy clean (CodeRabbit on #2362).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The window was fixed at 880 x 480. It now resizes from every edge and corner, down to 480 x 240 and up to the screen less a margin, and its header, sidebar and table follow its current size. Egui's memory keeps the size and place while the app runs.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Model-Effort: Opus 5.5 drove; Opus 5.5 briefed; Sonnet 5.5 wrote at medium
Change to swapped the instance's variant in place, so the next variant's After delay
kept the instance's node id and was already recorded as fired: the chain stopped
after one step. The swap now clears the fired keys inside the instance and records
when it happened; next_delay counts a timer from the later of the screen's arrival
and that swap.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Model-Effort: Opus 5.5 drove; Opus 5.5 briefed; Sonnet 5.5 wrote at medium
Both moves had names of the same length, so which one ran first came
from the order of the variables. The first one now has a longer name,
which the longest-first order always moves first, so the second one
always collides after a move that has to be undone.
The collision test's two moves had names of the same length, so the
first one already collided and nothing was left to undo. With the
existing name on the second move, the first moves, the second collides,
and the test checks that the batch puts the first one back.
Renaming a group in the Local variables window replaced every slash in the
typed name with a hyphen, so "Palette/Orange" gave a flat Palette-Orange
group and there was no way to move a group under a new parent.
The typed path now replaces the group's last part, so a slash nests the
group as in Figma: Orange/100 becomes Palette/Orange/100 and the sidebar
shows Orange under Palette. Each part is trimmed and empty parts are
dropped; a name that comes out empty or unchanged does nothing. The
renames go deepest name first, so a group moved into its own new subgroup
(Orange to Orange/Warm) never collides with a variable that is still to
move. A rename onto a variable name that stays is refused by
variable.update and the batch rolls back; it stays one undo step.