Comments on: SwingUtilities.invokeAndWait… doesn’t. http://blog.palantirtech.com/2008/02/21/invokeandnotwaiting/ Articles from the Engineering Group at Palantir Technologies Tue, 24 Jan 2012 09:51:18 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Rodrigo http://blog.palantirtech.com/2008/02/21/invokeandnotwaiting/comment-page-1/#comment-1063 Rodrigo Thu, 12 Jan 2012 14:46:51 +0000 http://blog.palantirtech.com/2008/02/21/invokeandnotwaiting/#comment-1063 I wanted to note that invokeLater(Runnable) doesn't throw an exception if run inside the EDT. Actually, the javadoc says explicitly (even in java 1.4 -- see http://docs.oracle.com/javase/1.4.2/docs/api/javax/swing/SwingUtilities.html#invokeLater%28java.lang.Runnable%29): "If invokeLater is called from the event dispatching thread ... (the runnable) will still be deferred until all pending events have been processed." So, actually the implementation of the runOnEDT(Runnable) method above doesn't prevent an exception, but actually affects how the runnable is going to be executed on the EDT: if we're on the EDT it is executed immediately; otherwise it's queued. I wanted to note that invokeLater(Runnable) doesn’t throw an exception if run inside the EDT. Actually, the javadoc says explicitly (even in java 1.4 — see http://docs.oracle.com/javase/1.4.2/docs/api/javax/swing/SwingUtilities.html#invokeLater%28java.lang.Runnable%29):

“If invokeLater is called from the event dispatching thread … (the runnable) will still be deferred until all pending events have been processed.”

So, actually the implementation of the runOnEDT(Runnable) method above doesn’t prevent an exception, but actually affects how the runnable is going to be executed on the EDT: if we’re on the EDT it is executed immediately; otherwise it’s queued.

]]>