Printable View
Hi
Just having a slight problem writing a simple Snake game (just in command view, with cout<< etc.
I have most of the game finished, but i got to trying to get input.
The game was working fine until i added GetAsyncKeyState, and added: #include <windows.h>. Then the game still compiled, just as soon as it opened it threw an error.
Any suggestions?
Is there any way i can get Keyboard input without using windows.h, and without having to wait for the input?
Thanks
What error? What's the code? What's the debugger saying?
hmm... u see, thats the problem. It doesn't give much info about the error.
The debugger says nothing...the program compiles well with no problems. Just that as soon as i add #include <windows.h>, and compile and execute the program, a msgbox comes up saying "Error, log created". I think its a Dr. Watson error, if that helps.
However, i don't have the code here atm, will post later when i run it again
Have you actually used a debugger on the app?
here's the error i get:
"snake.exe has generated and will be closed by Windows. You will need to restart the program.
An error log is being created"
The bad thing is that i am making int on a school computer, so:
1) I can't access debugging
2) I can't access the error log
attached is the .cpp file...
Compiled and ran fine for me (except I couldn't move the snake, but I didn't check to see why, or if I was pressing the right buttons)
And what does it look like with GetAsyncKeyState added?
BTW, since system() creates a new process, it is awfully slow in computer terms. Maybe you can find an alternative.
Check the PauseClock() funciton....
Thats where there's a pause to have correct frame-rate, and any input is received...
The GetAsyncKeyState funciton is there too...
oh, and sunburnt, it doesn't fully work yet, but when it does i'll post it again uf u want me too. U see, this is for a tutorial i will be running, so any flaws in my code (when finished) it would be good if other picked them up :p
Oh, right...
I remember many problems with GetAsyncKeyState in console programs. Very many. The never got resolved. Sorry, don't know how to help you there.
It definitly shouldn't crash though...
There is something you can do with input buffers which doesn't block, let me try it out and get back to you.
ok, i think it must be something to do with the school's network restrictions. I got it working fine at home, but the same error pops up whenever i the same code at school.
Probably not allowed to #include <windows.h>, cos i could be hacking, not that I know how... :p
Is there any other way to get key input? I've seen stuff like kbhit() and getchar(), but never in a working program....
this is the fault of schools/colleges being totaly retarded and not actualy alowing you to use anything that is even remotly usefull.. they will block out ANYTHING that will allow you to make a decent prog, but anything that you wont normaly use... they allow...
some at the college i go to
Could simply be a faulty windows.h too, or faulty include libs. That actually sounds very probable.
Unfortunatly the thing I tried did not work.