quote:Original post by rypyr
Anybody remember how bioskey(0), bioskey(1) and getch() are supposed to work exactly?

Urf, that brings back some unpleasant memories.

Bioskey(0) waits for a key press, and returns its code. I don''t remember the format of the code, though IIRC, it''s 16 bits. The right arrow was ~19232 IIRC.

Bioskey(1) does the same thing, but doesn''t wait, so it''s generally the one you want to use in a "real-time" game.

Getch(), you should get some documentation for it on the web. It returns the character pressed. I don''t think that it can distinguish between keys that don''t return a character. It returns a char, IIRC again.

But bioskey() was too weak; you can''t tell if two keys are pressed at the same time (unless it''s a combination with shift/control/alt --- which is why they were popular "jump" keys). The real manly way is to get the keyboard data straight from the keyboard port

Cédric

Bioskey, IIRC, doesn''t work with the "state", but rather with key presses.

If you hold the right arrow down, but then start holding the up arrow, you will receive the code associated to the up arrow. There will then be no way to tell if the right arrow is still being held down.

Now that I think about it, I remember the need to call bioskey(0) when there is a key being pressed, otherwise the buffer would get full (and you would get the familiar PC speaker BEEP). Bioskey(1) doesn''t affect the buffer. I don''t really remember the specifics, unfortunately.

Cédric