React to a sortable layer's blending mode changing at runtime (the
LayersPanel compose chain — spec §5.4). Wired for all four geometry
types.
Switching TO a sorted mode cannot simply "register+sort": the
SortWorker has no centers for a node that was order-independent at its
last commit (registration is gated on the live mode, and the staged
arrays were transferred/discarded). Instead, clear the node's noop
stamp (userData.committedData) and request a view reprocess — the
memoized-concat noop path would otherwise skip re-projection entirely.
The resulting standard commit registers + sorts like any other (the
SliceCache still holds the source nD data; one O(N) re-projection per
mode switch, a rare user action).
Switching AWAY just stops future sorts (a sorted order is harmless
under commutative modes — no identity reset needed); the worker-side
centers are released as hygiene.
React to a sortable layer's blending mode changing at runtime (the LayersPanel compose chain — spec §5.4). Wired for all four geometry types.
Switching TO a sorted mode cannot simply "register+sort": the SortWorker has no centers for a node that was order-independent at its last commit (registration is gated on the live mode, and the staged arrays were transferred/discarded). Instead, clear the node's noop stamp (
userData.committedData) and request a view reprocess — the memoized-concat noop path would otherwise skip re-projection entirely. The resulting standard commit registers + sorts like any other (the SliceCache still holds the source nD data; one O(N) re-projection per mode switch, a rare user action).Switching AWAY just stops future sorts (a sorted order is harmless under commutative modes — no identity reset needed); the worker-side centers are released as hygiene.