Well I know that if I grab and click hold the separator bar in the  
Browser window
just above the senders button, then count to five, I count 80,000  
signals
to the semaphore, which is spining that ioProcess loop really really  
fast...
As you mention both processes do this together so nothing really gets
stacked up. However this is needless work...


PS I've see the glitch pause usually when the cursor has been changed  
in the
browser windows, can't say how or what it is doing yet.

> Given that the io process runs at a higher priority than the polling  
> process
> (which is the case for all uses of Sensor I am aware of) this is  
> impossible.
> The signal will be served right away by releasing the io process (note  
> that
> since the polling process is running the io process _must_ be waiting  
> on the
> semaphore). So there's definitely no grinding through pending signals  
> going
> on here.
>

--
======================================================================== 
===
John M. McIntosh <johnmci at smalltalkconsulting.com> 1-800-477-2659
Corporate Smalltalk Consulting Ltd.  http://www.smalltalkconsulting.com
======================================================================== 
===