> Only after the 3rd pass it is much quicker. Seems like the performance may be > related to the visibility status of the canvas. Any other recommendations.
Makes sense that, while the image isn't visible, the changes are much faster: in an optimized environment, they (basically) occur at DOM level only. Once the image is displayed are they rendered, which explains the delay in 2nd pass. I'm not acquainted with Batik's internals but I believe that's what you are experiencing. I'm assuming that "Only after the 3rd pass" means "after the 2nd pass" as no 3rd pass was described... > Any other recommendations. Recommendations in which sense? What do you intend? That measured times are more predictable (equal to each other) or to simply speedup the slower case(s)? If only a speedup is intended you may try using suspendRedraw/unsuspendRedraw before many known dynamic updates, although (again) I'm not very familiar with Batik (and I believe they are internally called already [2]). Also, nothing is stated whether you are using Java or Javascript (within SVG scope) to perform these operations... Regards, Helder Magalhães [1] http://www.w3.org/TR/SVG/struct.html#DOMInterfaces [2] http://markmail.org/message/c26wj5ncaetgzs5j --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
