To: DJGPP AT SUN DOT SOE DOT CLARKSON DOT EDU, dj AT ctron DOT com
From: A DOT APPLEYARD AT fs1 DOT mt DOT umist DOT ac DOT uk
Date: 27 Aug 93 16:56:53 GMT
Subject: Cat and mouse games

  How common is clash between Gnu C and GO32 and the mouse? Does it happen
only with particular makes of PC, or particular makes of mouse? Much of the
memory-clash-causing bulk of existing mouse handlers is concerned with
operations such as (finding where the mouse is on the screen) and (making a
mouse pointer on the screen), which (as far as I can tell from examining
source forms of Gnu C libraries) are ignored by Gnu C graphics routines, which
instead merely reads (button activity and) how many mickeys (= mouse movement
units) moved and works out mouse position for itself and makes its own visible
mouse pointer. This I feel that it would help if someone could write for each
of the common sorts of mouse a mouse handler specifically for use with Gnu C,
engineered not to clash with anything that Gnu C and GO32 etc uses, and not
bothering to do anything except to record and report (a) button activity and
(b) mickeys moved since last time the mouse condition was read.