Hi the.networker,
Note that you haven't provided most of the information asked for (hardware and software environments, goal, etc.): partial response in accordance... :-| > public class Test extends JFrame implements Runnable,UpdateManagerListener [...] > Element tempE = > jSVGCanvas.getSVGDocument().getElementById(Integer.toString(random.nextInt(22500))); This hints towards you are using numerical identifiers. Note that, as far as I know, in XML and identifier [1] must not start with a number... I'd suggest something like "rectNNNN" or simply "rNNNN". Although this is probably only being used for the purpose of testing, this might help (that is, weird behavior may occur in other implementations). Have you tried suspending the rendering (before entering the "for" loop) as suggested in my previous message? I'm half certain that doing that within the update manager thread already takes care of that, but my knowledge of Batik internals is pretty rough regarding this sort of thing. Probably Thomas or Cameron can provide much more interesting feedback regarding optimizing the code. > What I am trying to do right now is just to evaluate Batik and find out the > best possible performance, kind of Batik rendering world record:-) It depends on what you intend. As already stated, moving rectangles has a purpose of testing something which might be accomplished in a completely different way... > I want to avoid getting stuck in the middle of development in a big project > in the future because of performance issues. This is a wise thing to do. :-) Hope this helps, Helder Magalhães [1] http://www.w3.org/TR/REC-xml/#id --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
