🚀 go-pugleaf

William Yu wrote:

> You need a separate thread to listen for user interface events and
> interrupt the processing loop when necessary. (Interruption can be in
> the form of setting boolean flags that the processing code periodically
> checks against.)

  William-

I'm kind of confused with this and can't seem to find any other documentation
on it.  I've played around with some multi-threading, but I'm not sure how to
go about plugging a UI listener into a new thread class and still have it
update the components.  For example, I have a while loop reading down a
database, taking the contents and dumping it to a text file. As it's reading
each row, I have a TextControl component saying "Exported x Records".
Something like:

      while (true) {
        if (datamod.queryDataSet.atLast()) {
          break;
          }
        iCount++;
        tcExportCount.setText("Exported "+iCount+" records.");

        dataOutputStream.println(datamod.queryDataSet.getString("AnyField"));
        datamod.queryDataSet.next();
        }

  Now, the tcExportCount TextControl component will update fine throughout the
rest of the program until it hits this loop!  But all refreshing stops until
the loop is complete.  (This also holds true for a KLGroup ProgressMeter
component).  I've tried refresh(), update(), repaint(), etc on the frame and
components with no positive results.  (I'm on JBuilder 2).

I've tried building a thread class that does nothing but run monitoring the
datamod.queryDataSet to know what record is being accessed then having it post
it's information (via passing to the thread the tcExportCount object) to the
UI while the the loop above is running.  The thread runs as it should, but
still will NOT update the UI!

I've gotten my cancel button to work this way though, and I appreciate the
help with that!

Any clue where I can look up some examples for UI refreshing?

Thanks again-

Scott Ottesen
sottesen@dced.state.ut.us
or
sottesen@wasatch.com