Reply to thread

Message: [QUOTE="Hal Vaughan, post: 2010478"] Thanks! I'm beginning to get a feel for this. If activate() and deactivate() have separate threads within them, won't that take care of that? In other words, the EDT thread calls activate(), and within activate() I use SwingUtilities.invokeLater() and put the thread in there to update the GUI? That would still be using a different thread, but just within the method called instead of outside. It may not be much of a difference, but it would make the coding when I use that class easier. Also, as I've experimented, I've found that if I put any GUI updates within a Runnable() that is called with SwingUtilities.invokeLater(), those functions are not done until after the doExtensiveThings() routine is called. What do I do if I want to update the Swing GUI, THEN doExtensiveThings(), then update the GUI again? It seems invokeLater() does such a good job at invoking later all GUI work that it calls is held until the other stuff is done. That makes it hard if I want to start with a message to the user saying, "This could take a while, please wait..." Is there a way to repaint/refresh the GUI first, then do the work? Again, thanks! Hal [/QUOTE]