Handling the Event Dispatch Thread

Question

I have a question about the \'Event Dispatch Thread\'. I have a Main class that is also a JFrame. It initialises the rest of the components in the code, some of them do not

Answer 1

That is the way all the examples from the Sun tutorial work. Read the section from the Swing tutorial on Concurrency for more information on why it is done this way.

Answer 2

That is generally sufficient until you start making use of background threads for calculations, data acquisition, etc. Then you need to start being careful to verify that you are on the EDT prior to altering a swing component or its model.

You can test whether you're executing on the EDT with:

    if (SwingUtilities.isEventDispatchThread()) {
        // Yes, manipulate swing components
    } else {
        // No, use invokeLater() to schedule work on the EDT
    }

Also, see the SwingWorker class for details on how to hand off work to a background thread and process results on the EDT

Answer 3

This is the way to go. The only thing you should be careful about is if a listener that you register with the Swing components will spawn a new Thread (often for carrying out some long computation). Such new threads will need to use invokeLater if they are to carry out GUI operations.

Answer 4

Devon_C_Miller's answer is correct. I just want to point out a shortcut to invoking the event dispatch thread.

Here's how I start all of my Swing applications.

import javax.swing.SwingUtilities;

import com.ggl.source.search.model.SourceSearchModel;
import com.ggl.source.search.view.SourceSearchFrame;

public class SourceSearch implements Runnable {

    @Override
    public void run() {
        new SourceSearchFrame(new SourceSearchModel());

    }

    public static void main(String[] args) {
        SwingUtilities.invokeLater(new SourceSearch());
    }

}

You can copy this to every Swing project, just by changing the names.