Date: Sun, 23 Apr 2000 09:52:51 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Sahab Yazdani <beyonder69 AT geocities DOT com>
cc: djgpp AT delorie DOT com
Subject: Re: my mouse driver..
In-Reply-To: <3901C823.C3B39CF3@geocities.com>
Message-ID: <Pine.SUN.3.91.1000423095231.2139P-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Sat, 22 Apr 2000, Sahab Yazdani wrote:

> Hello everybody.. I've written a mouse event handler in DJGPP which for
> the most part works extremely well in either Graphics or Text based
> video modes, except that the darned thing is way too sensative.  A
> single average click of the mouse results in roughly 5-10 software
> clicks in a program that I write with my driver.

I'm not sure this is relevant to your problem, but the code you posted
doesn't lock the used_registers variable that is passed to your
MouseHandler function (nor did you include the declaration for this
variable in the posted snippet).

Also, I think you want _go32_dpmi_allocate_real_mode_callback_iret,
not _go32_dpmi_allocate_real_mode_callback_retf.  See section 18.8 of
the FAQ for a working example of a mouse handler.