Hervé Girod wrote:
>
>> By the way, I have another problem, I'm sure entirely due to me. I
>> subclassed the DOMViewer class in order to be able to modify the SVG
>> Document and its associated GVT tree when performing actions on the
>> tree. The first actions I tried to implement was deletion in the GVT
>> tree. I basically use the following approach :
> >
>> - then call this piece of code when clicking delete on a node of the
>> DOMViewer tree :
>> Node domNode = ((NodeInfo)treenode.getUserObject()).node;
>> Node parentNode = domNode.getParentNode();
>> parentNode.removeChild(domNode);
>>
>> And it is not working. I invariably have a LOT of exceptions in
>> removeChild in Batik code (stack pointer, etc...). I'm sure I haven't
>> understand at all how to use dynamic documents, so my approach must be
>> wrong, but where ?
> The above looks fine, care to share the stack traces?
To give you an "interpretable" stack trace, I tried to code the smallest
possible test case, devoid of all my specificities ... and in this case,
there was no change of the GVT tree at all, but no errors.... Then I tried
my main code, same thing, something I modified without being aware of must
have change a lot. After a while, I understood my mistake :
somehow (without being aware of it), I called (indirectly) the
renderGVTTree() method of JGVTComponent without releasing the ImageRenderer,
this leading to a Stack overflow exception at the end.
But may be I don't use the good way to call this method. In my case, I call
explicitely a forceRepaint() method in my subclass of JSVGCanvas which does
only :
renderer = null;
renderGVTTree();
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
