When you do heavy task you should run them in another threads rather in the same as gui. If you run in Event Dispatch Thread then the gui is gonna freeze until finish. You can use SwingWorker here is an example i really like Swing Worker Example Example: class Worker extends SwingWorker<String, Object> { @Override … Read more
A good rule is that all operations (access/updates/…) should happen on the EDT. There are a few exceptions mentioned in the javadoc (certain methods of certain classes), but they are so hard to remember that it is easier to stick to the ‘do everything on the EDT’ approach. Exceptions will not be raised (luckily, JavaFX … Read more
NEVER call the sync function on the main queue If you call the sync function on the main queue it will block the queue as well as the queue will be waiting for the task to be completed but the task will never be finished since it will not be even able to start due … Read more
99% of the time either code will work. However, Swing was designed such that all updates to Swing components should be done on the Event Dispatch Thread (EDT). Read the Swing tutorial on Concurrency for more information. The problem is the 1% of the time when it might not work. You don’t want to waste … Read more
Your showProgress method is being executed within the context of the Event Dispatching Thread. The EDT is responsible for, amongst other things, processing paint requests. This means that so long as your for-loop is executing, the EDT can not process any new paint requests (or handle the invokeLater events either) as it is blocking the … Read more
The EDT exception handler doesn’t use Thread.UncaughtExceptionHandler. Instead, it calls a method with the following signature: public void handle(Throwable thrown); Add that to MyExceptionHandler, and it should work. The “documentation” for this is found in EventDispatchThread, which is a package-private class in java.awt. Quoting from the javadoc for handleException() there: /** * Handles an exception … Read more
This is the official reference: Swing’s Threading Policy In general Swing is not thread safe. All Swing components and related classes, unless otherwise documented, must be accessed on the event dispatching thread. And the repaint method does not “document otherwise”. To doubly reassure you that you do not need to look any further than an … Read more
It is a known bug as acknowledged by Oracle Bug ID:6924233 The JOptionPane apparently causes another event to be generated with a check box value = false. The recommended fix is to instantiate the JOptionPane using invokeLater. Submitted On 09-MAR-2010 The change is in the BasicButtonListener – Method focusLost() In 1.6.0_18 it is … ButtonModel … Read more
The problem is, your long running task is blocking the Thread that keeps the GUI responsive. What you will need to do is put the long running task on another thread. Some common ways of doing this are using Timers or a SwingWorker. The Java tutorials have lots of information regarding these things in their … Read more
Although the Swing concurrency tutorial already contains some very good samples on how to deal with concurrency in Swing, find below an example which contains a checkbox to prove the UI is still alive has a progress bar, which gets updated from the SwingWorker has a label, which gets updated once the SwingWorker is finished … Read more