Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!samsung!think.com!paperboy!osf!dbrooks From: dbrooks@osf.osf.org (David Brooks) Newsgroups: comp.sys.atari.st.tech Subject: Re: Getting ASCII value from scancode Message-ID: <21493@paperboy.OSF.ORG> Date: 29 Apr 91 12:04:40 GMT References: <21491@paperboy.OSF.ORG> <1991Apr29.083347.12706@informatik.uni-erlangen.de> Sender: news@OSF.ORG Reply-To: dbrooks@osf.org (David Brooks) Distribution: all Organization: Open Software Foundation Lines: 26 csbrod@immd4.informatik.uni-erlangen.de (Claus Brod) writes: >dbrooks@osf.osf.org (David Brooks) writes: > >>entropy@gnu.ai.mit.edu (entropy) writes: >>/* Now, if you have the scancode right justified in int scode... */ >> >> shifts = Getshift(); /* i.e. kbshift(-1); > >You don't have to call kbshift; the keyboard status is returned in one of >the evnt_multi return parameters. True; my code assumes Bconin(), and I had missed the fact that the original question had referenced evnt_multi(). > 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. -- David Brooks dbrooks@osf.org Systems Engineering, OSF uunet!osf.org!dbrooks Donnie Wahlberg is brought to you by three billion years of evolution.