Thread: Update GUI before lengthy task

A gui should not become un-responsive due to a long task running.

If you're using a Swing layered design you can loop through all components which have been added to a particular component.

JPanel somePanel = new JPanel();
// .. add a bunch of stuff to that somePanel
 
// disable everything on somePanel
for(Component c : somePanel.getComponents())
{
    c.setEnabled(false);
}

Similarly, you can automatically re-enable everything using the same technique.

I would recommend running your task on a separate thread. To simplify your job, have the separate thread do the disabling/enabling of components.

This solution has the benefit of allowing you to leave certain components active (say for example if you wanted a cancel button) and make your gui more user-friendly (no one likes a non-responsive window). It may very well be easier to design, too.

I agree with helloworld. But you might also look into using a GlassPane to restrict user input (informatively, not annoyingly).