🚀 go-pugleaf

From article <$dougn.64.0@sasb.byu.edu>, by $dougn@sasb.byu.edu (Douglas R. Nebeker - MIS_SAS):
> 
> I'm building a mouse trap of sorts....
> 
> Actually, I just want to know if the mouse is being used (like the 
> _good_ screen saver TSRs out there--they don't blank your screen when no 
> keyboard input is coming in as long as the mouse is being moved).
> 
> I've successfully hooked the serial port interrupt (Int 14h?) and the mouse 
> interrupt (Int 33h).  The mouse works like it always has, but my variable 
> 'busy' never gets changed... (actually, that's a lie--when the mouse is 
> initialized, busy=M, but while the mouse is moving and buttons are being 
> pushed, busy doesn't get changed)
> 
> My question then is this:  is there another way to access the mouse besides 
> through Int 33h?  Does each mouse driver use a different Int for their 
> driver?  Do I need to hook the DOS int 21h too?

Many programs that use the mouse do not poll the driver for position
and button state. They use the asynchronous notification functions of
the mouse driver. With these, you set up a mask of events you want to
be told about and the driver calls a routine in your program to tell
you about the event. All kinds of restrictions on what the event handler
routine can do, but better than polling in many cases.

You will need to insert yourself between the driver and the program's
event handler.
-- 

Ed
ekalenda@netcom.COM