I had what seems to be the same problem.
I *think* it might be related to concurrency issues because:
This seems like a good bet. Jean are you passing off the modification of the document to other threads?
You could also put a trace statement in the code that is
supposed to remove the graphics node from the rendering tree.
It is in batik.bridge.AbstractGraphicsNodeBridge.handleDOMNodeRemovedEvent.
This is normally called from the BridgeContext's DOMNodeRemovedEventListener.
- sometimes GVT peers are properly removed from the GVT tree, and sometimes not, I did not find a 100% reproducible test case.
- Debugging step by step produces different results (usually the correct ones)
Jean-Christophe ARNU (JX) wrote:
Hi,
I use a SVG file, where I put dynamically a g element (as child of the Node named "place" in the tree). This g element is made of 500 elements (text,
circles, xlink, a). This g element is a "layer". My application has to remove
this layer on a user command (I use a popup menu item for this). In the
removal method, I use place.removeChild(myGElement) in a RunnableQueue.
My problem is that my g element is no longer in the DOM tree but is still
rendered (even if I put other elements in the DOM tree or zoom or pan) : I
PrintWritered into files the DOM tree to make comparitions...
What can I do to force my removed DOM element not to remain rendered onto the
SVGCanvas?
Thank you :)
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
