Hello David,
Thanks for your example. I reproduced your problem, and I'm now
investigating. I will come back to you when I will have more information
to give you.
David Kane wrote:
> We are also working on extending the JSVG canvas to give us some basic
> animation capabilities. We are triggering the update from a Javascript
> event. What is weird is that each time we reload the DOM, we seem to
> double our Javascript event handlers. The attached code illustrates the
> problem. The code will open the enclosed SVG document. Everytime you
> click the blue rectangle, it will write out a message to System.out and
> then reloads the document. The first time you click the rectangle, you
> get one message. The second time, two messages, the third time 4
> messages, etc.
>
> I wonder if this is related to Chris Kelly's note. Our context is a
> little different (we are triggering events from the SVG document itself,
> and Chris is triggering events from an external button), but I wonder if a
> proliferation of event handling objects (or something related) is the
> source of the object leak?
>
> I'm using Java 1.3.1, and I get the same results from both Batik 1.0 and
> Batik 1.1RC1.
>
> Any suggestions?
--
Christophe
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
