Hi all,

In my Swing application I have a JButton on a JPanel that tells the program
to save a large array of data to disk.  The process takes about 10 seconds,
so I pop up a simple JDialog showing how far along the process is.  I'm
creating and showing the JDialog, then using SwingWorker() to do the save as
a background thread so the UI thread doesn't hang.  Inside construct() I'm
updating a JLabel on the JDialog with some descriptive text about where it
is in the process.  This works perfectly.

But I have a bit of a Catch-22 situation.  Since the JDialog isn't modal,
it's still possible to click the JButton "underneath" the JDialog and start
*another* thread doing exactly the same thing in parallel.  Not good.

However, if I set the JDialog to be Modal, the main thread stops when
.setVisible() is called, of course.  So the background thread never gets
started.

Any suggestions?  Is there a better way to go about this?

Thanks much,
Leif