Re: Debugging Question

From:

Nigel Wade <nmw@ion.le.ac.uk>

Newsgroups:

comp.lang.java.programmer

Date:

Fri, 14 Sep 2007 15:21:14 +0100

Message-ID:

<fce5cr$pad$2@south.jnrs.ja.net>

RFleming@NationalSteel.com wrote:

This *might* be the Swing/EDT problem.
Look into SwingWorker.invokeLater(Thread) method, &
<http://java.sun.com/docs/books/tutorial/uiswing/concurrency/index.html>

Indeed that was the problem. I am somewhat new to JAVA, not
programming. I was forced to learn 'by fire' Java when another person
left the company, and I inherited a program, it did not use the
swing.invokelater for the progress bars, and they get updated twice a
second, which occaisonally caused stack trace errors, but the program
ran fine. I added the Swing.invokelater thread and the errors went
away.

Thanks for your assistance!

If this application is a vital one, and you need to get it right, then it's
definitely worth you taking the time to read the Java/Swing Tutorial. There is
a section dedicated to progress bars, and also another on threads in Swing.
http://java.sun.com/docs/books/tutorial/uiswing/components/progress.html
http://java.sun.com/docs/books/tutorial/uiswing/concurrency/index.html

You might want to re-visit the code afterwards and verify that its use of
threads is valid given that you've already found one misuse.

--
Nigel Wade, System Administrator, Space Plasma Physics Group,
University of Leicester, Leicester, LE1 7RH, UK
E-mail : nmw@ion.le.ac.uk
Phone : +44 (0)116 2523548, Fax : +44 (0)116 2523555