summaryrefslogtreecommitdiff
path: root/test/process/mounts.zig
diff options
context:
space:
mode:
authorGabriel Schneider <[email protected]>2026-11-05 13:28:13 -0300
committerGabriel Schneider <[email protected]>2026-11-05 15:23:49 -0300
commit23c9932afe9bbf01aa84d780e9030dfb6e333475 (patch)
tree01f801fe4e9f286cc44eb8ad206ed4ab8585ab77 /test/process/mounts.zig
parent1b2ac091200e9192f3677abe161217ba82463606 (diff)
downloadpardes-23c9932afe9bbf01aa84d780e9030dfb6e333475.tar.gz
pardes-23c9932afe9bbf01aa84d780e9030dfb6e333475.zip
effects out, the theme crossfade: a theme change takes the chrome at once, as it always took the content; colors.ChromeAnimation (its OKLab steps, its retarget, the ticks and the frames it asked of nextWake) goes, Pardes.chrome is the theme's chrome, set as the theme changes, and the `animate` flag goes from loadThemeFile and applyThemeEffect with it, as does the build's -Dtheme-animation option (and its place in the wire's fingerprint); no frontend fades a theme of its own (a window crossfading every cell's colour for 160 ms is a copy of the last frame kept and blended, for one keystroke's change); the fade's tests go, the PDF test loses its ticks through a fade, and `core animation keeps wall time at 60, 120 and 144 Hz and across a stall` goes with the one animation that ran it; the perf baselines lose the option from their build identity; GUI goldens 16-debug and 17-terminal change, the golden session having faded its themes by default: a fade's frames kept the Debug word's announcement up in the picture's pane, which gave up a row to it under the Debug box; the tree before this change built with -Dtheme-animation=false draws exactly these frames, all sixteen byte for byte
Co-Authored-By: Claude Opus 5.5 <[email protected]> Claude-Session: https://claude.ai/code/session_016Y9MNAtZenFv4weoMD3cge
Diffstat (limited to 'test/process/mounts.zig')
0 files changed, 0 insertions, 0 deletions