🚀 go-pugleaf

Tad Frysinger <tfrysinger@earthlink.net> wrote in message
news:MPG.116405e456424a169899a8@forums.borland.com...
>In article <36D28D4D.4F81E9D2@teamworks.de>, mschmitz@teamworks.de
>says...
>> hi,
>>
>> you should read the swing documentation carefully!!!!!!!!!
>>
>> the progressbar can't be updated, because you're doing all the work
>> inside the event-dispatching thread. that means the messages for
>> repaint,validate a.s.o. don't get processed until your method finishes!
>> the only save and clean solution is to use a thread to do all your
>> processing (try the worker class available at java.sun.com) and call the
>> progressbar.setValue method from this thread!
>> martin
>>
>Just saw your example - this is also *not* what you are supposed to do.
>Make sure that you update the progress bar from your second thread so
>that it places the update request in the event thread's queue.  Check out
>the SwingUtilities.invokeLater() method.
>
>Otherwise, another window (or some other [paint event) will end up
>deadlocking you.
>
>Tad Frysinger
>[TeamB]

I've looked at that piece and am now confused. do I call invokeLater on the
second thread, or from the second thread. If the latter, then what am I
calling invokeLater on??
-------
Frank Packenham
Senior Analyst/Developer
NeuroFlex Pty Ltd.