🚀 go-pugleaf

Steve wrote:

> "pNichols" <paul@computer-logic.net> wrote in message
> news:3fecff09$1@newsgroups.borland.com...
>> there was a good article this month In Java Developer's Journal about
> Swing
>> and Listener events performance probems that you might want to take a
>> look at. I think it could address some of your issues.
> 
> Thanks for the tip. It covers about the same ground as the Sun tutorial,
> albeit with more example code. It did nudge me to look at the source for
> SwingWorker, though. Since the finished() routine is run by invokeLater,
> it should be attached to the end of the queue. Since this doesn't always
> have the effect I intended, it strengthens my suspicion that this was just
> lack of forsight in the way that JComboBox was written (i.e., the list
> should be retracted before it calls the action event handler).

There are a myriad of problems with Listeners and Event classes in Java
Swing. I constantly monitor my programs to see how many iterations they
make through an ActionEvent or WindowListener which will fire not only on
these events but any subsequent events within the same inner class. I think
Javasoft DEFINITELY needs to revisit the way they implement these Listener
classes.