0.9.0-beta.19Beta

Changed

• Rolling back, restoring and an agent's edits no longer redraw the whole page on the GPU canvas, in the cases a review meets. Layers inside a card with a shadow, a blurred frame or a group casting a shadow, the card itself, and layers a rollback or a restore brings back are now written straight into what the canvas shows, and a shadow or blur is drawn again only when what it shows changed. On a generated page of 20,002 layers in the shape of a real game document: none of an agent's 24 batches redraws the page (15 did); rolling back a step and the step built on it takes about 0.09 s (0.15–0.21 s), restoring it about 0.08 s (0.21–0.23 s), and rolling back a whole 23-batch session about 0.19 s (0.32–0.35 s), which is still slower than it should be. (F-333)
• Jumping to a layer from the Changes tab shows it at once. The first frame at the new zoom comes in about 0.06 s (0.8–0.9 s before), a little soft for a moment; the sharp picture follows once the view holds still. Zooming through several levels with Ctrl+wheel gets the same, so it no longer stops at each level to redraw the page. (F-333)
• The Changes tab opens and redraws faster. What depends on rolling a row back ("3 later steps build on it") is now worked out just after the tab is drawn, or at once for the row you point at; layer icons drawn as their shape are no longer rebuilt after every change. The tab opens in about 0.03 s (0.09–0.16 s). (F-333)
• Compare builds its pictures' documents faster. It no longer copies every layer of the frames it pictures: on that page, a step across ten frames compares in about 1.0 s (1.4–1.7 s), and a change in the largest frame in about 0.18 s (0.24–0.26 s). (F-332)
• Shapes with areas draw faster in exports, thumbnails and agent images. A frame no longer re-reads each shape's segments and areas to find it unchanged. Nine 1,012-segment grids with 484 areas each now draw in about 1.6 ms, down from about 3.5 ms, which is faster than the same shapes without areas (about 2.6 ms).

Fixed

• A layer moved and then faded or given a new stroke colour could jump back to where it was on the canvas, until something made Polyform redraw the whole page. GPU rendering only. (F-337)
• After Polyform's text glyph store filled up, every edit redrew the whole page until something else redrew it. Nothing was drawn wrong; it was only slower. (F-338)
• A shape with areas you recoloured could stay drawn in its old colour on the canvas, in exports and in agent images, until the shape itself changed or the file was reopened. The file always held the new colour. In every beta since beta.9. (F-339)