Thomas DeWeese wrote:
Hi Jorg,
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.
Stack during logo removal
Thread [RunnableQueue-0] (Suspended (breakpoint at line 211 in Client$4))
Client$4.run() line: 211
RunnableQueue.run() line: 199
HaltingThread(Thread).run() line: 534Stack during data appending
Thread [RunnableQueue-0] (Suspended (breakpoint at line 329 in Client))
Client.updateMap(MapUpdate) line: 329
Client.access$7(Client, MapUpdate) line: 300
Client$4.run() line: 228
RunnableQueue.run() line: 199
HaltingThread(Thread).run() line: 534Both are in the RunnableQueue, i switch to it using getUpdateManager().getUpdateRunnableQueue().invokeLater(new Runnable()...)
I'm not sure what the Client.access$7 means during data appending, does this signify a different thread? It seems to point to a line where i am fetching the updated data from the documentfragment.
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.
Yes but if this is the case than my appended data wouldn't show at all would it ?
Anything lowlevel i can do to get to the bottom of this?
Thanks Jorg
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
