> From: John.Maloney at disney.com
> >From:  Dean Swan at MITEL on 11/22/99 01:02 PM
> >What seems to be happening is that when the VM calls
> >'MsgWaitForMultipleObjects()' in from 'ioMousePoint()' with a  
wait timeout
> of 5
> >ms, the E-105 will actually wait for up to 50 ms if no events get  
queued.
> >Touching the screen with the pen must queue up enough events to  
cause it to
> >return nearly immediately.
>
> Just as I suspected! I've seen this behavior under quite
> a number of OS's. Basically, the OS takes the opportunity
> to slow the processor or do something else, since it figures
> you're just waiting for an event anyhow.

Well, just about any multitasking OS I know will also only guarantee  
a lower bound for waits.  50ms sounds a lot like the minimum  
execution quantum, so if you lose the processor due to waiting you  
may just have to wait for that amount of time.

Marcel