mirror of
https://github.com/storytold/vectorcraft.git
synced 2026-10-14 19:26:56 -04:00
dotCooCoo
9f0a9a362b
The renderer kept the outline of a stroke under the address of the stroke in the object's appearance, the bits of the width and the tolerance level, and used an entry only when the entry held the object being drawn. The slices of a gradient along or across a stroke were kept the same way. Objects can share one appearance until one of them changes it. Copies made by Duplicate Selection share the original's appearance, gradients included. For objects without a gradient fill or stroke, so do the art the renderer places for unstained symbol instances, the copies a live repeat draws and copies made by edit.duplicate. In each frame, the objects that share an appearance replaced each other's entries. The renderer therefore outlined their strokes again in every frame. The two caches now key each entry by the address of the object as well, and each object keeps its own outlines from frame to frame. Art that the renderer makes again in every frame keeps the old key: symbol art that placed_art does not keep, and the evaluations of live objects and the art of objects with effects that their caches do not keep. The copies in such art replace each other's entries as before. vectorcraft-cli bench of 2,000 unstained instances of a symbol of eight paths took 45.7 ms a frame on main and 31.1 ms with this change, at 2880x1800 on 8 threads, and a grid repeat of the same paths, which draws 2,000 groups, took 45.0 ms on main and 27.2 ms with this change. The peak working set of a bench run on the instances went from 88 MiB to 122 MiB. In the tests, each frame draws what a new renderer draws.