From:	"Mr A Appleyard" <MCLSSAA2 AT fs2 DOT mt DOT umist DOT ac DOT uk>
Organization:	Materials Science Centre
To:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>, DJGPP AT delorie DOT com
Date:	Fri, 22 May 1998 08:15:45 GMT
Subject:	Re: BUG in Gnu C++ (djgpp v2) mouse access under Windows 95
Message-ID:	<16844584E2C@fs2.mt.umist.ac.uk>

On Thu, 21 May 1998, Mr A Appleyard wrote:
> I can't easily change AAEMACS.EXE or SPATRL.EXE to polling the mouse (=
> repeatedly asking for the mouse's pointer coordinates and the states of its
> buttons), as I found that (at least under DOS 6.22) polling the mouse in a
> tight loop makes DOS or its keyboard handler ignore the `special characters'
> (ALT combinations, F1 to F12, grey keys, and similar) from code 128 upwards.

  Eli Zaretski replied:-
> Please post the shortest program that shows this. GNU Emacs polls the mouse,
> but can nevertheless read all the keys generated by the MF-II (i.e. 101-key)
> keyboards, so this is possible, at least in principle. You seem to imply
> that your programs read keyboard via DOS. If this is indeed true, it's
> different from Emacs which uses the BIOS.

  AAEMACS reads the keyboard by "AX=0x0700; call interrupt 0x21; return
AX&255; if this == 0, repeat and it is a special keystroke". It acted deaf to
special keystrokes 128 to 255 until I changed it from polling the mouse to
supplying a hook routine. Please how does Emacs read the keyboard by BIOS?
  SPATRL.EXE reads the raw key events by hooking interrupt 9. Does the new
version of V2 have any plans to supply the raw keystrokes to the user?, since
I heard that djgpp Gnu C++ hooks interrupt 9 anyway as part of trapping the
ctrl-C breakin event. What has come of the code to do this, that I sent to one
of the djgpp email groups a while ago?

- Raw text -