after reading http://java.sun.com/docs/books/tutorial/uiswing/mini/threads.html,
i have some doubt:

consider:

====== this code is running in another worker Thread ======

       //  SwingUtilities makes sure code is executed in the event
thread.
       SwingUtilities.invokeLater(new Runnable() {
              public void run() {
                  progressBar.setValue(50);
              }           
       });

===============================================

SwingUtilities.invokeLater is to ensure any GUI update code to be
performed in the event dispath thread.

1. Why we to explicitly put the progressBar.setValue(50) inside the
SwingUtilities.invokeLater? i thought the call itself to
progressBar.setValue(50) ALONE inside a user thread, will "Schedule A
Task To Event-Dispath Thread To Update The Progress Bar".

2. Inside the user thread, we have to explicitly put every single GUI
update code to the SwingUtilities.invokeLater. isn't that is a bit
cumbersome? imagine we have thoundsand of line of GUI update code in a
single thread, then we have to make thousand call to the
SwingUtilities.invokeLater.

consider:

==== this code is running in another thread===

        // long processing........ blah blah blah

       SwingUtilities.invokeLater(new Runnable() {
              public void run() {                            
                  progressBar.setValue(1);
              }           
       });
       
       // another long processing........ blah blah blah

       SwingUtilities.invokeLater(new Runnable() {
              public void run() {                            
                  progressBar.setValue(2);
              }           
       });

       // another another long long processing...... blah blah blah
       SwingUtilities.invokeLater(new Runnable() {
              public void run() {                            
                  progressBar.setValue(3);
              }           
       });

===============================================

thank you.

regards
yan cheng