do :A$ = right$(inkey$,1):print A$,asc(A$):loop until A$ = chr$(27)
He just did show you..
Not what I ment, the example of tabling Cosines and Sines has no relation ship to this code which mearly prints the iformation of a pressed key. Even if you did table INKEY$, you'd still need to know which was which key....
but nm, no need to start a flame over a simple question.
Ironicly, I have been using similar constants for the past couple of months since I started coding most projects in FB, so it just helps to prove my point that you don't know these things properly if you rely on tables like the above.
This table is for QBasic....
And in FreeBASIC you have the multikey() option,.. Is it wrong to use the table included in the gfxlib document to find the correct hexadecimal for the key you need? Or the premade header file so you can use the key lable?
matt2jones wrote:.....
All I'm trying to say is it's better to know how to work out an answer then to have a load of answers written infront of you and keep copying them off.
And in FreeBASIC you have the multikey() option,.. Is it wrong to use the table included in the gfxlib document to find the correct hexadecimal for the key you need?
Okay, What the flying fork?!?!?
Why?... Why?
I can't even summon the strength to anwer that...
we were talking about mother fork qbasic
This entire fork thread is about INKEY$ for qbasic
I, along with the rest of the world, use said files with a clear concience. That is not what I am arguing about.
Repeat:
I am not trying to diss/convert you or your way of life. We are on the same side.
if you wanna insult me, have the decency to PM me or something.