Re: Need simple example of how to safely pass data from worker to EDT swing threads.

From:

Lew <lewbloch@gmail.com>

Newsgroups:

comp.lang.java.help

Date:

Thu, 6 Dec 2012 11:10:38 -0800 (PST)

Message-ID:

<848c30ed-2727-429e-a1ba-d85133a755ff@googlegroups.com>

Nigel Wade wrote:

Although this may not solve the problem you were previously having,
which is most likely caused by having too many objects in the JComboBox.
You will still have the same number of objects in the JComboBox when
SwingWorker.done() is completed.

When you open the JComboBox the EDT has to render all 3000 objects into
the popup list.

Unless one needs all 3000 or 5000 entries on screen at the same time, it might
not be necessary to fetch them all into the GUI widget at once. There is a technique
called "windowing" or "cursoring" (to verb some nouns).

For such a small number of items via I/O as yours, you can pull them into an abstract
model that feeds the GUI model, say a map or list or other collection. When the screen
needs a view into that abstract model, let's say items k through k+99 inclusive, you
feed those items into the GUI model along with some housekeeping variables to locate
where the window is within the complete data structure. (Via the techniques others
have already described to keep GUI on the EDT and non-GUI off the EDT.)

So the GUI only knows about a manageable number of entries at any one time. This will
work if copying small amounts of data into the GUI model is faster than displaying
large amounts at once in the GUI model.

--
Lew