Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!olivea!uunet!math.fu-berlin.de!fauern!faui43.informatik.uni-erlangen.de!csbrod From: csbrod@immd4.informatik.uni-erlangen.de (Claus Brod) Newsgroups: comp.sys.atari.st.tech Subject: Re: Getting ASCII value from scancode Message-ID: <1991May1.170724.6241@informatik.uni-erlangen.de> Date: 1 May 91 17:07:24 GMT References: <21491@paperboy.OSF.ORG> <1991Apr29.083347.12706@informatik.uni-erlangen.de> <21493@paperboy.OSF.ORG> Distribution: all Organization: CSD., University of Erlangen, Germany Lines: 23 dbrooks@osf.osf.org (David Brooks) writes: >> Use this value instead of the kbshift >>value to be sure to get a consistent view of the things going on at the >>keyboard and in the AES keyboard buffer. >Yes, there is a window between Bconin() and Kbshift(), but it's an utterly >unimportant one. There's also a little overhead in the extra BIOS call. >Incidentally, what does evnt_multi() do; does it call Kbshift(), or does it >know where the BIOS stores the current shift bits? Just wondering. evnt_multi does many things, and it even seems to buffer keyboard events in some manner. Moreover, it's just the recommended method for sampling the keyboard when using AES functions. Internally, the AES calls the VDI, and the VDI probably calls BIOS, but nobody knows exactly what else goes on. ---------------------------------------------------------------------- Claus Brod, Am Felsenkeller 2, Things. Take. Time. D-8772 Marktheidenfeld, West Germany (Piet Hein) csbrod@medusa.informatik.uni-erlangen.de Claus Brod@wue.maus.de ----------------------------------------------------------------------