Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!elroy.jpl.nasa.gov!decwrl!fernwood!uupsi!sunic!chalmers.se!etek.chalmers.se!etek.chalmers.se!fabian
From: fabian@etek.chalmers.se (Martin Fabian)
Newsgroups: comp.sys.atari.st.tech
Subject: Re: Simulating keypress
Message-ID: <1991Apr8.160108.22367@etek.chalmers.se>
Date: 8 Apr 91 16:01:08 GMT
References: <1991Apr5.151946.25763@etek.chalmers.se> <1991Apr6.000637.20676@jato.jpl.nasa.gov>
Sender: news@etek.chalmers.se (USENET News System)
Reply-To: fabian@contrl.chalmers.se (Martin Fabian)
Organization: Chalmers University of Technology, Gothenburg, SWEDEN
Lines: 30


In article <1991Apr6.000637.20676@jato.jpl.nasa.gov>, vsnyder@jato.jpl.nasa.gov (Van Snyder) writes:
|> I'd like to get hold of keypresses.  It's easy to get hold of mouse
|> motions by inserting your own handler in place of the mousevec in
|> the struct returned by XBIOS' kbdvec function.  But how do you get
|> hold of keypresses?  Must you intercept the keyboard packet handler
|> and interpret all the packets?
|> 
|> Thanks in advance,
|> 
|> 
|> -- 
|> vsnyder@jato.Jpl.Nasa.Gov
|> ames!elroy!jato!vsnyder
|> vsnyder@jato.uucp

This seems like exactly my problem. Since the ikbdsys, address of
which is also returned by kbdvec, reads the keys off the UART there
really does not seem to be any other way of doing that. The difference
between the mousevec and the keyboard routines, is that the mousevec
is passed the address of the mouse packet, whereas the keyboard routine
is not (or do I have that wrong ?).

Perhaps you could intercept the actual interrupt routine in some way ?

M Fabian, fabian@contrl.chalmers.se
          fabian@etek.chalmers.se

"Nuclear arms can wipe out life on earth, if used properly."
                                                   (D Byrne)