Skip to main content
GameDev.net gamedev.net
🔒 Locked

Odd Termination Behaviour

Started by BtySgtMajor Jan 17, 2003 at 8:42 AM 0 replies 400+ views
Original Post
BtySgtMajor
BtySgtMajor
Hi there, I''m sure this question has probably been asked sometime in the past, but, here goes anyways. In my ''game'', when I hit escape it''s supposed to quit. It has worked in the past without failure numerous times...When I check for the escape inside my game class (called from the main game loop in WinMain in my main.cpp), I post the WM_DESTROY message and specify that, if it takes a few cycles to actually quit and this game class is called again it is not to do any processing or rendering. Now, I''ve recently added more graphics to the screen; more specifically, a tile "map" that occupies most of the screen. However, when I now hit escape, the game basically locks and I have to wait for it to stop responding to manually shut it down. Any thoughts? Thanks for the insight!
jhavna
jhavna
I''m not an expert on this (as i don''t know much about windoze messaging) but it appears that your app is stuck somewhere.. possibly in a loop out of which it can''t get out. Have you tried debugging it and setting a breakpoint on the exit routine and seeing where the code goes to? Are you also destroying all your objects and freeing all your allocated memory?

let me know what you find.. or if that helped... If it didn''t help, keenp shtum

"Without a sense of humour we couldn''''t react to a lot of things"
-----------------------"Without a sense of humour we couldn't react to a lot of things"

Topic Locked

This topic has been locked by a moderator. New replies are not allowed.

Sign in to reply to this topic.