Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!elroy.jpl.nasa.gov!decwrl!deccrl!bloom-beacon!eru!hagbard!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: <1991Apr11.160849.14152@etek.chalmers.se>
Date: 11 Apr 91 16:08:49 GMT
References: <1991Apr5.151946.25763@etek.chalmers.se> <1991Apr6.000637.20676@jato.jpl.nasa.gov> <1991Apr8.160108.22367@etek.chalmers.se> <3032@krafla.rhi.hi.is>
Sender: news@etek.chalmers.se (USENET News System)
Reply-To: fabian@etek.chalmers.se (Martin Fabian)
Organization: Chalmers University of Technology, Gothenburg, SWEDEN
Lines: 14

In article <3032@krafla.rhi.hi.is>, adamd@rhi.hi.is (Adam David) writes:

|> You find the address of the raw keyboard buffer using the XBIOS function iovec.
|> Keyboard scancodes can then be inserted directly into the buffer. You will want
|> to disable interrupts or otherwise stop the real keyboard input while you are
|> simulating keypresses (if you prefer not to have mixed input). Whatever you put
|> into that buffer will be picked up by the BIOS the next time(s) it gets some
|> input from the keyboard device, just as if it was actually typed in.

OK, but does this also apply to evnt_keybd and evnt_multi ?
And what about the keyclick, the ikbdsys handles that. Fact ?

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