I'm still playing around with it, maybe the following is stil useful:
- when i resize the canvas *after* the initial logo is displayed, then the logo disappears when i append the data.
- when i resize the canvas *before* the initial logo is displayed then the problem appears again.
It seems that batik does not now that the logo is there until it somehow has to repaint the canvas.
Regards Jorg
Thomas DeWeese wrote:
Hi Jorg,
Jorg Heymans wrote:
I can't seem to isolate the problem, which probably indicates something smelly is going on with my DOM (remember the attribute namespaces!).
Can I do anything else to debug this? What would cause an element that is physically removed the DOM to still appear on the canvas?
Well my best guess is that you have a threading issue, you've already stated that this isn't a problem but I still suspect it is (of course I've been wrong before).
You might try printing out the current stack trace before you remove the logo and before you add the content and make sure they are rooted in the UpdateManager's RunnableQueue.
When the GVT tree is modified outside of the update manager thread (implying that the DOM is being modified outside of the update manager thread) you will get the 'disappears' for the next rendering behavior you are seeing.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
