About GetKeyState:
"The key status returned from this function changes as a given thread reads key messages from its message queue. The status does not reflect the interrupt-level state associated with the hardware. Use the GetAsyncKeyState function to retrieve that information."

Has this been changed, or what?

Quote: Original post by Wavarian
Great, just what we need. More trojan-horse programmers.

Take a look at his profile.

Think so, too. Opening/Closing CD-Rom, running in the background, getting key states without window, no taskbar icon, ....

Quote: Original post by Lyve

Quote: Original post by Wavarian
Great, just what we need. More trojan-horse programmers.

Take a look at his profile.

Think so, too. Opening/Closing CD-Rom, running in the background, getting key states without window, no taskbar icon, ....

my main interest in c++ is to create graphics and cool/usefull programmes, however occasionally i like to make some funny programmes to anooy my friends, which dont have any permanent damage, or implications, i only give the programme to selected people, and always provide a way to delete the programme, and finally, i always tell them how to delete the file as soon as it has run. I dont see anything wrong with this, and some of the stuff I find out about can be quite usefull, for future projects.

Quote:
About GetKeyState:
"The key status returned from this function changes as a given thread reads key messages from its message queue. The status does not reflect the interrupt-level state associated with the hardware. Use the GetAsyncKeyState function to retrieve that information."

Has this been changed, or what?

I'm not sure, but it seems to work, if the key is pressed, the return value is -127 or -128, if its not pressed the value is 0 or one.

Okay.