SwingWorker
is used for the following purposes:
- For running long-running tasks in a different thread so as to prevent the GUI from being unresponsive
- For updating GUI with the results produced by the long-running task at the end of the task through
done()
method. - For updating GUI from time to time with the intermediate results produced and published by the task with the help of
publish()
andprocess()
methods.
SwingUtilities.invokeLater()
can perform the above tasks as follows:
- Instead of executing
SwingWorker.execute()
method from the EDT, we can executeExecutorService.submit(new MyRunnable())
as it will also create another thread which can execute long-running task. - For updating GUI at the end of the task, we can put code (written in
done()
method of case1)SwingUtilites.invokeLater(new RunnableToExecuteDoneMethodCode())
at the end of the task. - For updating GUI in the middle of the task, we can put code (written in
process()
method of case1)SwingUtilites.invokeLater(new RunnableToExecuteProcessMethodCode())
at the place where we calledpublish()
method in case1.
I am asking this question because the problem specified in question Java - SwingWorker - Can we call one SwingWorker from other SwingWorker instead of EDT can be solved by SwingUtilities.invokeLater()
but can't be solved with SwingWorker
An important feature of the 1.6+ SwingWorker class is the EDT(Event Dispatch Thread) difference between doInBackground() and done(). You should think of doInBackground() as doWorkOutsideEDT() and done() as doWorkInsideEDT(). Run this instructional example to see the different.
Output:
SwingWorker
is a helper class -- it is not that you need to use it, but using it is much simpler and clearer than doing the same work by hand. (It also makes checking progress easier.) Note that it was added version 6 -- before then some people used a simpler class defined in the Swing Tutorial or did step similar to the ones you noted.