On Wednesday 02 July 2003 05:33 pm, John M McIntosh wrote:
> Why, well I suspect, mostly because I've not found it yet, is that
>   under the right sequence of events the mouse
> over logic is hunting for cursor movement via say cursorPoint which
>   calls primMousePt which calls
> inputSemaphore signal, and stacks LOTS of excess signals on the  
> Semaphore, at which point the
> io processor loop consumes them. The issue here is LOTS, that this
> is   reflected in a glitchy pause as we
> grind though them.
>
> However I'll listen to other suggestions.

That's fixable. There are a couple of places in SystemWindow's reframe 
code where it starts using "Sensor cursorPoint" and "Sensor 
anyButtonPressed" (partly in the Rectangle code that does the fast 
framing).

I think we could eliminate most or all of these.

-- 
Ned Konz
http://bike-nomad.com
GPG key ID: BEEA7EFE