Date: Thu, 27 May 1999 14:48:09 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: djgpp AT delorie DOT com
Subject: Re: intrrupt handler.
In-Reply-To: <374D0087.CB0E5F9C@geocities.com>
Message-ID: <Pine.SUN.3.91.990527144405.26821C-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Thu, 27 May 1999, Derek wrote:

> I know...I thought this would be faster than calling __dpmi_int(0x33,&regs)
> each time I wanted to know where the mouse was....

There is function 0Ch of Int 33h that allows you to install your function
as the handler for any mouse event.  Then the driver calls you instead of 
the other way around.  The FAQ shows an example of using this function.

> > Hooking the mouse through function 0Ch of Int 33h is much, much, MUCH
> > easier.
> 
> but isn;t it much much slower?

No, it isn't.  Why should it be?

Besides, since the mouse is an input device used by humans, the speed 
there is not that important.  It's not that the user could press the 
mouse 10,000 times a second, you know...