Thread: EventQueue.invokeLater VS SwingUtilities.invokeLater

From the SwingUtilities API: SwingUtilities (Java Platform SE 6)

public static void invokeLater(Runnable doRun)
...
As of 1.3 this method is just a cover for java.awt.EventQueue.invokeLater().

Originally Posted by devett

That's really not helping me. I've always used SwingUtilities.invokeLater(new Runnable); but recently installed Eclipse 3.7 Indigo and with the WindowsBuilder when you build a new JFrame project now it uses EventQueue.invokeLater(new Runnable); Is there a reason for this, or is it just a preference of style.

What is not helpful about it? The API already answered your question, and I even copied it here for you. There is no difference between the functions, as of 1.3.

Originally Posted by devett

I'm not trying to be arrogant sorry, I'm just trying to learn having come over from the .NET world. I tried to find the link, but I thought I read somewhere yesterday that they said when Swing was introduced SwingUtilities had a problem with possible deadlock on large appications, where the EventQueue would be more reliable. I know they work with the event dispatch thread at least I thought I remember this much. so I came here where I trust the experts. I appriciate your insight and just trying to learn all I can.

It's okay.

What you're saying may have been true before 1.3, but that was a long time ago. Now, the SwingUtilities methods simply call the EventQueue methods, so they're the same. But people continue to use whichever one they see in the tutorials (I use SwingUtilities), which may have been written before 1.3. But it really doesn't matter.