Conversion to png with svgexport does not wait for svg animation to finish

[maurimo]

Conversion to png with svgexport does not wait for svg animation to finish

[maurimo]

I didn't. Sorry, I think I currently don't have the time to look into this issue, in particular if it is and svgexport's bug...

…

On Sun, Feb 25, 2018 at 3:14 PM, Zevero ***@***.***> wrote: I am running kanimaji on linux debian with python 2.7. It seems svg frames are correct. I can display them for example on google chrome and after waiting for the animation to be finished the frame looks as intended. However the corresponding png frame looks as if shot half a second into the animation. I am afraid svgexport does not seem to wait for the animation to finish... Have you experienced this behavior? Yours, Severin — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#4>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAGHQ5guHXf9xJqV31xrQLDnph_Sd3v5ks5tYaLqgaJpZM4SSZT7> .

-- Atenciosamente, Maurizio Monge Instituto de Matemática da UFRJ, Av. Athos da Silveira Ramos 149, Centro de Tecnologia Bloco C Cidade Universitária - Ilha do Fundão Caixa Postal 68530 21941-909 Rio de Janeiro - RJ - Brasil http://im.ufrj.br/~maurizio.monge/wordpress/

[zevero]

Thank you for your response. I can understand, that you do not have any time. For documentation I provide my quick fix solution and direction for others who might experience this issue.

In svgexport in render.js:129 I need to set timeout to 20000 instead of 0. That way the animation is finished when the png file is rendered (no guarantee for more complicated kanji however).

Project svgexport did not have any commits since mid 2016 (as kanjimaji). The culprit seems to be phantomjs. I faintly can remember changes to the render timing.

Setting svgexport to 20000 is not very pleasant, as with 200 frames it would take me over an hour per kanji. Doing all 6743 Kanji would take approximately one year!

[zevero]

hm ... all 200 frames seem to be done in 20000 ms in parallel ... that was unexpected ... ok so it works