Path: news.cs.au.dk!Morten.Grouleff.Mjolner.Informatics From: Morten Grouleff Newsgroups: comp.lang.beta Subject: Re: Checking keyboard buffer Date: 17 May 1999 16:42:59 +0200 Organization: Mjolner Informatics. Lines: 26 Message-ID: References: <7hae06$qsm$1@nnrp1.deja.com> <7haek6$rdv$1@nnrp1.deja.com> NNTP-Posting-Host: freki.mjolner.dk Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Trace: xinwen.cs.au.dk 926952180 3233550 255.255.255.255 (17 May 1999 14:43:00 GMT) X-Complaints-To: news@cs.au.dk NNTP-Posting-Date: 17 May 1999 14:43:00 GMT X-Newsreader: Gnus v5.5/Emacs 19.34 Xref: news.cs.au.dk comp.lang.beta:11944 Andrew Klaassen writes: > In article <7hae06$qsm$1@nnrp1.deja.com>, > Andrew Klaassen wrote: > > > I want to build a function that checks for keyboard input, then (if > > there's something there) uses it, else (if there's not something > there) > > immediately moves on. > > ...and, I want to do it in the text-based linux version > of BETA. Still possible? If you use SystemEnv, you can make a system that waits for input, and have the rest of your program run in another system. Using this scheme you can get hold of a single character at a time. The only problem is that input does not get delivered until "return" is pressed, which is probably not what you intended... If you with to get round this problem, more drastic measures are necessary. Regards, -- ** Morten Grouleff: ** ** Earthworm Jim PC: ** ** Mjølner Informatics: **