Well, actually, it does return -1 on no key, scancode on keypress, and 1000+scancode on extended keys. Extended keys in crt report themselves as two keys, #0 followed by something else. Arrows are #0#70-something, so they would be returned as 1000+70(something), whereas 'A' would be returned simply as 65.
On Windows you can also use GetAsyncKeyState to get the state of a specific key using one of VK_[xxx] virtual codes and even detect whether the key has been pressed or not previously.
I would save readKey in a variable, because it is a complicated function? No reason to call it twice.
as far as i remember, readkey removes the key pressed from the buffer. if you press a special key, it will put 2 chars in the buffer: a #0 char and another char. the sequencial call to readkey will catch them. but i think this will not allow to have multiple keypress, as the buffer is very short, only 16 chars (at least in dos/windows i think). unless you manage to extend that buffer.
It's called a second time to catch the scancode.Originally Posted by User137
Posting Permissions
Reply With Quote
Bookmarks