Re: JDialogs launched outside the Event-Dispatch Thread

From:

Lew <lew@lewscanon.com>

Newsgroups:

comp.lang.java.programmer

Date:

Fri, 7 May 2010 07:55:11 -0700 (PDT)

Message-ID:

<a5d2488b-58df-4f73-a5e0-6097b48ce270@h9g2000yqm.googlegroups.com>

Marcin Rodzik wrote:

Being aware of what has been said <http://ow.ly/1I50nhttp://ow.ly/1I50J>
I'd like to ask explicitly: what should I do if I want to display some
information to the user in a Swing GUI app using a JDialog? I know
dialogs are event-driven so that execution of the thread which
requested displaying the dialog stops, but other currently fired
events are still handled.

The thing I don't know and I'd like to is: should I create a Runnable
object and schedule it for execution:

SwingUtilities.invokeAndWait(new Runnable() {
  @Override
  public void run() {
    /* display the dialog here */
  }

});

Usually the JDialog is raised in response to an event already on the
dispatch thread, but using invokeAndWait() or invokeLater() is fine if
you're already on the EDT.

I don't know why you'd prefer invokeAndWait() over invokeLater().

or:

I can simply write the code like this:

JOptionPane.showMessageDialog(parent, msg, title, messageType);

without the SwingUtilities stuff and Swing will handle the code
correctly anyway?

Only if you're already on the EDT to start with, otherwise it's a bad
idea.

I used to follow the first option but now I doubt if
it makes any sense.

Depends on whether you really mean for the caller to wait for the
dialog.

--
Lew