Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!elroy.jpl.nasa.gov!jato!jdickson
From: jdickson@jato.jpl.nasa.gov (Jeff Dickson)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: keyboard input
Keywords: fastest way needed
Message-ID: <1991May2.213909.13075@jato.jpl.nasa.gov>
Date: 2 May 91 21:39:09 GMT
References: <4HG28HR@cs.swarthmore.edu>
Reply-To: jdickson@jato.Jpl.Nasa.Gov (Jeff Dickson)
Organization: Jet Propulsion Laboratory, Pasadena, CA
Lines: 17

In article <4HG28HR@cs.swarthmore.edu> hinds@cs.swarthmore.edu (Alexander Hinds) writes:
>
>	I'm writing a program (game) in which I need to get keyboard
>input in the fastest way possible, ie. not through intuition.  (i'm
>doing this now, and getting alot of overhead.)  I was thinking of
>using the keyboard.device, but that would interfere with the input.device.
>So, does anybody have any ideas they could float my way?  Thanks.
>
>Alexander Hinds

	Why not instead insert your own custom handler into the input.device
event chain ahead of intuition (pri < 50). A handler can decide if the event
is to be propagated or not. When your window was the active one, you would
prevent intuition from seeing keyboard.device events, because you would be
handling them directly (by virtue you're ahead of intuition). 

	-jeff