process still running after quitting the app

[mskuma]

I guess we are at the end of the road here. I will probably omit the keyboard code (which is ok), or use the non-directx keyboard. It might be a bug, but it also might be something weird with my machine. I've done the virus, spyware & rootkit scans. Certainly does seem to be Direct X-related as I mentioned before that taking out WindowedScreen code avoids this problem. I think this issue could be a trap for someone in the future.

Anyway I appreciate your extensive help netmaestro. I also appreciate Trond's code since omitting the keyboard code was the key.

[Xombie]

Thanks Xombie.

Another thing to try on yours ... put ExamineKeyboard() before OpenWindowedScreen() and try it.

Interesting. I copied your code to try. I reformatted it to my anal specifications, dropping out the procedures and etc... Running it like that showed the same problem as the program stayed in memory. I put the ExamineKeyboard() line before OpenWindowedScreen(), ran it again, closed it and it immediately vanished from the process list. However, running your original code again did not give me the same problem. In fact, I never got the problem again. Even putting back the ExamineKeyboard() line.

One other thing I noticed is that when I got the problem of the program hanging in memory, it used roughly 19.5 mb. When it would correctly close out, it would only use around 3.2 mb.

And I didn't know ExamineKeyboard() used DirectX. I had thought it used GetKeyboardState_(). Huh.

[mskuma]

I put the ExamineKeyboard() line before OpenWindowedScreen(), ran it again

I'm not sure how that's possible. When I tried that, I get an error saying keyboard commands have to come after OpenScreen or OpenWindowedScreen.