Export did not produce the correct results about anigen

[aibosan]

I could not replicate this problem. You could try resetting the time to 0 and exporting again.

[doctormo]

Interesting, once closed, re-opened and set to zero as you say. The problem has gone away. I wonder what it was.

[aibosan]

SVG animations are problematic, as they work on various levels. Basically, XML animations (animate element) get written into the XML tree on the fly. But transformations (and motion along path) don't. CSS animations (also the animate element) also don't, but instead of an attribute in DOM, they have to be squeezed out of the browser's "calculated CSS values". Oh, and paths' "d" animations have to be calculated manually because google decided to phase out pathData, because... well... I don't know. They are just kinda stupid, I suppose.

Anyway. Because of this, when exporting, the animations have to be removed one by one, each time using the right approach to push the animated values into the XML tree. When this is done, the XML gets put through a canvas (which can't do most of the animations SVG can) to export the PNG. Since this method is destructive, the original SVG has to be cloned, but because animations might have already been running inside it, some of the XML data might have already been changed. Furthermore, once the XML gets cloned, there's no way to tell what the original values were.

I've been trying to find a solution for this, but each time I do, it breaks another aspect of the whole thing. Obviously, the method used in 0.8.0 isn't ideal either. Just keep this thing in mind if this kind of thing happens in the future, and try to avoid animations with non-zero value at t=0. Those can be an issue. Unless they're not. Like I said, it's a mess.