Re: strange getch+kbg- behaviour
- From: Richard Heathfield <invalid@xxxxxxxxxxxxxxx>
- Date: Fri, 22 Sep 2006 08:07:18 +0000
"simnav" <nospamtnx> said:
Richard Heathfield wrote:
+AD4- jacob navia said:
+AD4- +AD4- getch() probably expects an ASCII character, not just some
+AD4- +AD4- keyboard key
+AD4-
+AD4- That incorrect answer is a great example of why you should ask
+AD4- platform-specific questions on a newsgroup devoted to the
appropriate
+AD4- platform.
Please accept my apologies for the two mistakes I did: incorrect
newsgroup and multi post (my newsreader is driven crazy and sent it too
many times...)
Anyway Jacob response was wrong in ANSI context but seems to be correct
on dos/djgpp platform:
Not even correct in /that/ context, because Delorie followed Borland's lead
with getch, and Navia's response was incompatible with Borland C's
behaviour and therefore incompatible with DJGPP's behaviour. You'd be
better off finding out how to use DJGPP's getch in a DOS programmers'
newsgroup.
getkey() resolved the problem.
....but didn't teach you why getch() didn't behave as you expected. You might
want to chase that down, in the interests of understanding what on earth is
going on.
--
Richard Heathfield
"Usenet is a strange place" - dmr 29/7/1999
http://www.cpax.org.uk
email: rjh at above domain (but drop the www, obviously)
.
- References:
- strange getch+kbhit behaviour
- From: simnav
- Re: strange getch+kbhit behaviour
- From: jacob navia
- Re: strange getch+kbhit behaviour
- From: Richard Heathfield
- Re: strange getch+kbg- behaviour
- From: simnav
- strange getch+kbhit behaviour
- Prev by Date: Re: Help me
- Next by Date: Re: convert argv[1] to hex
- Previous by thread: Re: strange getch+kbg- behaviour
- Next by thread: Re: strange getch+kbg- behaviour
- Index(es):
Relevant Pages
|