Date:	Mon, 30 Aug 93 10:19:15 CST
From:	(csaba AT vuse DOT vanderbilt DOT edu) <csaba AT vuse DOT vanderbilt DOT edu>
To:	A DOT APPLEYARD AT fs1 DOT mt DOT umist DOT ac DOT uk
Cc:	djgpp AT sun DOT soe DOT clarkson DOT edu
Subject:	Re: Cat and mouse games

On 27 Aug 93 16:56:53 GMT,
  <A DOT APPLEYARD AT fs1 DOT mt DOT umist DOT ac DOT uk> writes:

>  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.

Based on the number of bug reports I received clashes of the above type 
are very rare. You may want to experiment with your configuration: install/
uninstall EMS, change the mouse driver (if you can use the driver of a 
different mouse with yours) etc..


Csaba Biegl
csaba AT vuse DOT vanderbilt DOT edu

- Raw text -