Tom Fjellstrom <tomcf@...> writes:
> Am I right in guessing that the X (mickey) mouse driver
> doesn't support showing the mouse on a memory bitmap?
> It works perfectly fine if i show_mouse(NULL) or
> show_mouse(screen), but not for any mem bitmap.
Showing mouse on memory bitmap might not work correctly, if bitmap
size is larger than screen and mouse range is set to this size. In
such cases you can try to add a call to get_mouse_mickeys somewhere
in a loop, so it is called at least once per second. Then mouse
handler will be switched in different mode and mouse should be able to
move anywhere in the bitmap.
>From <allegro-owner@...> Sun Nov 21 21:53:32 1999
Received: from sutra.merton.ox.ac.uk [18.104.22.168] by canvaslink.com with ESMTP
(SMTPD32-4.06) id A02A1F8A014C; Sun, 21 Nov 1999 21:53:30 -0400
Received: (from gfoot@...)
by sutra.merton.ox.ac.uk (8.9.3/8.9.3) id CAA17905
for allegro@...; Mon, 22 Nov 1999 02:52:02 GMT
Date: Mon, 22 Nov 1999 02:52:02 +0000
From: George Foot <george.foot@...>
Subject: Re: [AL] Allegro just for DJGPP?
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.4us
In-Reply-To: <19991121.195536.-112919.0.roberts.j.whitlock@...>; from Robert S Whitlock on Sun, Nov 21, 1999 at 07:55:33PM -0500
On Sun, Nov 21, 1999 at 07:55:33PM -0500, Robert S Whitlock wrote:
> > > Should I just put the inlclude directories in the path, or would
> > that
> > > leave a bad variable of "which include folder"?
> > Adding them to the include path is the correct thing to do.
> > When you call gccw32 this is done automatically; however, this
> > tool calls cpp directly. Stupid.
> Is the include path the same as where you type at the prompt (or
> autoexec.bat) PATH=c:\blah\blah; or is it something different?
It's different -- it's specified in DJGPP.ENV. You can do it in
the environment too though, and your path will get included too:
I'm not sure whether the C include path is the correct one to
use, but it probably is.