Date: Tue, 18 Jun 1996 08:34:04 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: newhallw AT escmail DOT orl DOT mmc DOT com
Cc: djgpp AT delorie DOT com
Subject: Re: MouseTrapping: An old problem revisited...
In-Reply-To: <9606172139.AA07370@cvfive>
Message-Id: <Pine.SUN.3.91.960618083143.15901I-100000@is>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


On Mon, 17 Jun 1996 newhallw AT escmail DOT orl DOT mmc DOT com wrote:

> I just recently got back into the DJGPP mailing list and was wondering what
> the current status of an old problem is...A few months ago I was building
> a GUI interface and was trying to redirect mouse interrupts to call GUI
> routines.  I was successful in getting my driver to modify some global variables
> but I was not successful in triggering function calls because it caused
> stack complications.
> 
> Has anyone successfully redirected mouse interrupts to code which calls
> other 32-bit(djgpp compiled) functions?

There is a mouse function that can be used to register a user-defined 
function that will be called by the mouse driver when certain 
user-defined events (such as mouse click or mouse movement) happen.  
Isn't this what you are after?  If so, then this is doable in DJGPP.