Re: Swing application architecture question.

From:

Tom Anderson <twic@urchin.earth.li>

Newsgroups:

comp.lang.java.gui,comp.lang.java.programmer

Date:

Sun, 24 May 2009 22:00:50 +0100

Message-ID:

<alpine.DEB.1.10.0905242159250.13653@urchin.earth.li>

On Sun, 24 May 2009, Mark Space wrote:

Lew wrote:

Mark Space wrote:

One thing I've seen other folks mention is to queue up events like this,
and process them in a batch on the EDT. You don't want to call the EDT
for every little thing. If you call it within about 250 milliseconds,
users won't notice the delay, and if you queue up many events in that
time, then you can update a bunch of objects in one go. Supposedly much
faster this way.

I'd consider some queue of Runnables, that every 250 milliseconds you wake
up and drain the queue on the EDT. Bonus points if the EDT task isn't
called unless there's at least one Runnable in the queue.

Doesn't the AWT infrastructure do that on its own if you use invokeLater()?

My point was to provide an explicit delay. I don't think invokeLater
does that.

Point. Although i would have thought that id the EDT was busy, the
invokeLater tasts will pile up at the back of the queue, and the effect
will be much the same. If it's not busy, then speed is not an issue.

tom

--
I hate to advocate drugs, alcohol, violence, or insanity to anyone,
but they've always worked for me. -- Hunter S. Thompson