Mail Archives: djgpp/1999/05/27/06:47:27
Eli Zaretskii wrote:
> On Tue, 25 May 1999, Derek wrote:
>
> > whoops..sorry..a couple mistakes...I corrected them but it stiil doesn't
> > work....
>
> Define ``doesn't work''. Otherwise, how can you expect us to help
> you?
I'm assuming its not installing my ISR....
>
>
> I also think this is a very inefficient way of hooking the mouse. You
> are intercepting the COM1 communications port (presumably connected to
> a serial mouse). This means you will have to handle all the
> communications with the mouse yourself, instead of letting the mouse
> driver handle it. Even the mouse cursor won't appear and won't move
> unless your program creates it, puts it on the screen, and then moves
> it whenever the mouse reports movement. In effect, you will be
> writing your own mouse driver.
I know...I thought this would be faster than calling __dpmi_int(0x33,®s)
each time I wanted to know where the mouse was....besides It'd be nice to know
how to do this anyway...
>
> And then, of course, some (many?) modern PCs use a mouse that plugs
> directly into the system bus, in which case you won't see anything
> useful coming your way through COM1.
>
ya...many...but it would still be nice to know....
>
> Hooking the mouse through function 0Ch of Int 33h is much, much, MUCH
> easier.
but isn;t it much much slower?
--
Derek
- Raw text -