| delorie.com/archives/browse.cgi | search |
| From: | mejm2 AT hermes DOT cam DOT ac DOT uk (Michael Meeks) |
| Newsgroups: | comp.os.msdos.djgpp |
| Subject: | Re: Allegro & shift keys |
| Date: | 3 Mar 1997 15:00:58 GMT |
| Organization: | Downing College, Cambridge, England |
| Lines: | 19 |
| Message-ID: | <5fep3a$sgr@lyra.csx.cam.ac.uk> |
| References: | <3315CEEB DOT 133F AT search DOT van DOT wa DOT us> <kNVa0OA27zFzEwI8 AT talula DOT demon DOT co DOT uk> |
| Reply-To: | mejm2 AT cam DOT ac DOT uk |
| NNTP-Posting-Host: | hammer.chu.cam.ac.uk |
| Originator: | mejm2 AT hammer DOT chu DOT cam DOT ac DOT uk |
| To: | djgpp AT delorie DOT com |
| DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
A more interesting ( possibly ) question is : why does the K/B hardware react like this : If <shift> is down, and then <arrow up> is pressed, The interrupt handler receives : <extended shift> off, <arrow up> down ? This really cocks up handlers that use the same map for extended and normal keys. ( By extended I mean a dual code thing 0xA0, code ( perhaps ) ). Is there any logical reason for this / is this a figment of my imagination ? Regards, Michael Meeks. -- mejm2 AT hermes DOT cam DOT ac DOT uk <><, Pseudo Engineer, itinerant idiot ...
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |