Only how I get the mouseFocus set is a bit of a puzzle and I want to 
move the handleXXX methods out of the UI object and into the dispatcher 
to prevent "accidental" overrides that hose up core mechanisms (like 
balloons and halos).

Plus, halting the UI thread is pretty dangerous. More often than not I 
hang the system. I've nearly got it working nicely - think I'll stay 
with it. Later when its really stable, I might remove the second thread 
and have the queue method simply dispatch.  Haven't decided.

I wasn't aware of the doOnlyOnce: method, looks like I reimplemented it 
on a per-object basis.  Thanks for the tip.

On Wednesday, July 30, 2003, at 10:47 AM, Andreas Raab wrote:

> To me this sounds precisely like what you get when you would simply 
> set your
> brick as the current mouse focus. Have you tried this? Might be easier 
> to
> figure out than a multi-threaded version.