🚀 go-pugleaf

Brian.Brunswick@cl.cam.ac.uk (Brian Brunswick on ely.cl.cam.ac.uk) writes:

> Could it be that you are relying on the callbacks being sequenced?
> I'm not at all sure that they are... I remember using a test program
> with callafters and callbacks, but don't know which one of the two
> was mixing things up?

  You are right, callbacks are not guaranteed to occur in any order or time
interval. Thats not the problem. The Callback code is *always* being called
properly and indeed the code being called doesn't care which order the data
comes in, all the information needed is contained in R12 passed to it by the
OS on entry.

> What happens if two events happen before the callback goes off?

   The two get enqueued and whichever one comes in last is the one noticed
the most by the user. (As far as I can tell that is) The problem is not so
much that the events are detected but that the OS seems to be not receiving
them *after* my code has finished doing the initial processing. Indeed
presuming for a second that even only one CallBack is permitted during heavy
loads this shouldn't affect the code or the OS as I reset the flags on exit
from the EventV code. (I assuming that the V flag would be set if the
Callback couldn't be arranged.)

   What makes it stranger is that the same code handles mouse and keyboard
events and it is *only* the mouse events that are suffering. All key presses
are making it through just fine.

    Philip

--
Philip R. Banks  Syntax: mail < banks_p@kosmos.wcc.govt.nz >            @@@@@/|
                                                                        @@@@/#|
                                                                        @@@/##|
I breathe the air, While they're running in a rat race,                 @@/---|
Way above it all, Standing on higher ground. ---A.P.P.                  @/    |