dotCooCoo 092f28feb3 Canvas: each document keeps its own placed-bitmap value in the frame key ...

The canvas cache key held the process-wide placed-document bitmap
generation, so a bitmap made for a file that only another document holds
changed every document's key, and the next frame differed from the
frame shown in more than the view. In the web build, which has no render
worker, a heavy canvas then rendered in the middle of a pan instead of
waiting until the view was still. On desktop the pan dropped its
low-resolution fill, and the render worker did not copy pixels from its
last frame.

Each document now keeps its own value, checked once per generation
change, as the plug-in key is. The value moves to the current generation
when the document shows a placed document of a file whose bitmap was
made. A file kept only for Undo does not count. When more bitmaps were
made since the last check than are recorded, the value moves when the
document shows a placed document of one of its images. After the
value moves, the part of the frame to draw again comes from the bitmaps
made since the last check before the move, so bitmaps made earlier for
other documents no longer make the whole frame render.

The canvas tests that retried or tolerated a new frame when another test
made a bitmap now assert without those workarounds.

2026-11-12 10:38:06 -08:00

..

src

Canvas: each document keeps its own placed-bitmap value in the frame key

2026-11-12 10:38:06 -08:00

tests

Fix Flatpak updates and bump to 0.24.1 (#6649)

2026-11-11 21:30:40 -05:00

build.rs

docs: tidy agent, contributor and asset docs

2026-10-31 04:17:23 +00:00

Cargo.toml

perf(canvas): zero-copy texture upload and progressive worker frame acceptance (#4615)

2026-11-02 14:36:07 +07:00