🚀 go-pugleaf

In article <1004@husc6.harvard.edu>, wen@husc4.HARVARD.EDU (A. Wen) writes:
> I've been mulling over ways to do non-blocking keyboard reads without
> polling the keyboard; is there any way that I can be signalled when the
> console device has input available short of creating a new task to block 
> for input and then signal its parent process?
> 
> That is, if I am waiting for the timer to wake me up, but I need to be notified 
> of any keystrokes that may occur in the meantime, is there anything simple
> (short of busy-waiting) that I can do?
> 

You could do it several ways. If you are using windows with IDCMP you might
wait for VANILLA or RAWKEY messages (whichever you put into the IDMCP Flags).
What I think you missed is the fact that you can do *asynchronous* device io.
Use the console device. This will decode the keyboard correctly and give you
funtion keys as well. You SendIO READ requests to the console device. The
device will signal you when it has something to deliver. When you get the
signal you get the reply with WaitIO(). There is an example in RKM Libraries
and devices. If I'm not mistaken it also works. 

------
Robin Rosenberg,	Abo Akademy, FINLAND
email: <rosenbergr@abo.fi>