Re: using threads

From:

Lew <lew@nowhere.com>

Newsgroups:

comp.lang.java.programmer

Date:

Sat, 30 Dec 2006 10:31:07 -0500

Message-ID:

<U8qdndvRlPTfGwvYnZ2dnUVZ_qunnZ2d@comcast.com>

Daniel Pitts wrote:

You may have to move some things around in your program, Since you are
using threads, you need some sort of callback mechanism (such as the
addResultToList method, as I called it here). Its important to use
invokeLater, so that any GUI manipulation happens on the Event Dispatch
Thread. (google Swing and Threads)
Also look up SwingWorker. It wasn't a part of the standard Java
distribution, but you can find a copy of it easily online.

Brandon McCombs wrote:

That direction of flow (bottom up the way I view it) is the opposite of
how I would prefer it because it makes the callback more difficult. ...

So somehow I
now have to make the lowest level worker object be responsible for
bypassing my stack of classes to update the GUI? That seems convoluted
to me. Or am I thinking totally the opposite of what I should be?

I seem to think I now have to tell my worker object that uses a thread
about my listmodel so that when it gets the data from its search
operation it has to be the one to update the listmodel. That means I
have to pass a reference of my listmodel through 3 classes so that the
worker object knows about it.

There has to be a better way.

There very well may be, but the point of putting the GUI update in the EDT is
ineluctable. It is a requirement of the Swing framework.The point of taking
long work *out* of the EDT is vital also. Any solution must take these into
account.

- Lew