Question

I was looking at some example code of GUIs in Java, and I was wondering what the proper way to display a GUI. Suppose a createAndShowGUI() method is written for some GUI. I saw something like this:

public static void main(String[] args) {
    javax.swing.SwingUtilities.invokeLater(new Runnable() {
        public void run() {
            createAndShowGUI();
        }
    });
}

Would it be wrong simply to call createAndShowGUI() at the end of the main method without the javax.swing stuff? Or I guess my real question is about what is going on here. I’m familiar with threads but I am not sure why it’s necessary to make a new thread (is that what’s going on here?) to display the GUI.

Answer 1

All interactions with the UI (Swing or AWT) MUST be executed from within the context of the Event Dispatching Thread.

Swing (and AWT) components are not thread safe, changing any of them from any thread other the EDT can lead to corrupted updates, paint artifices, dead locks and possibly crash the VM. They are also notoriously difficult to debug.

You might like to have a read through

• The Event Dispatch Thread
• The Single Thread Rule in Swing
• Will the real Swing Single Threading Rule please stand up?

I should also add, when the main method is executed, it is running in what ever thread the VM created for it. This is guaranteed not to be the EDT, as it will not have begin started until it is needed.

This is why good Swing programs always start with something like EventQueue.invokeLater. You could also use SwingUtilities.invokeLater, but it’s generally the same thing.