On 5/7/07, jalex <[EMAIL PROTECTED]> wrote:
That was originally what I tried, but all of my methods that modify the DOM, including the one that flips the visibility of layers, themselves do their work in in update manager's thread, so calling them naively causes them to get queued after the serialization thread. I just added code that checks if we are already running in the update manager thread, and if so, skip the enqueing. Works great. This is just like the EventQueue.isDispatchThread() boilerplate I have in some of my Swing code - don't know why that didn't occur to earlier. Thanks!
Great! Neat solution. Along similar lines... in some cases I've had methods add their DOM modifications to a List<Runnable>, instead of queueing them directly, so that all the updates can be aggregated into a single composite update (i.e., a single call to RunnableQueue.invokeLater()). This helps sometimes when you want the screen to redraw "all at once" instead of in pieces. __________________________________________________________________________ Archie Cobbs * CTO, Awarix * http://www.awarix.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
