dotCooCoo 08e1b7af80 Image Trace: a background trace applies only to the pixels it traced ...

A trace made away from its command (the background trace, #3098) counted
as current when the object, its image record and the settings were
unchanged, without looking at the image data. When other pixels came to
sit under the same image key (Rasterize after an undo reuses the key and
the id, Update Link, a replaced blob), the finished trace applied its old
paths to the new image.

The trace's inputs now include the encoded bytes it decodes, compared by
allocation first and then by content. TraceRun::current and the hand-off
in imageTrace.make and imageTrace.makeAndExpand both use them, so a stale
trace is dropped and the command traces the pixels there now. Equal bytes
in another allocation still count as the same image.

2026-11-13 07:18:53 -08:00

..

examples

…

src

Image Trace: a background trace applies only to the pixels it traced

2026-11-13 07:18:53 -08:00

tests

Merge pull request #7046 from dotCooCoo/fix/issue-3349

2026-11-13 16:04:36 +07:00

Cargo.toml

Data Recovery: on Windows the lock file check compares file identity

2026-11-11 16:59:13 -08:00