Windows message for closing application

Started by
11 comments, last by red_sodium 20 years ago
quote:Original post by red_sodium
...this is what a lot of tutorials do...
Another reason why tutorials are a bad idea. It is better to localize your message handling in the window procedure (which is in a parallel thread) rather than right in your main loop. The only "message handling" you should do in the main loop is the minimum necessary to pump messages.

quote:I don''t think this is the cause of my problem though, neither place produces the messages.
Time to crack out the debugger.
Advertisement
Thanks for that, Oluseyi. I must admit I know very little about my debugger that comes with Borland C++ Builder (v3.0). Do you know any good articles for this compiler or for debugging theory in general, as I'm a little rusty and it's hard to find good material on this subject without shelling out £50 on a 500 page hardback.

Thanks

PS: Would that really solve my problem? I'll give it a try anyway...

[edited by - red_sodium on March 26, 2004 8:26:59 PM]
"Learn as though you would never be able to master it,
hold it as though you would be in fear of losing it" - Confucius
LRESULT CALLBACK WndProc(HWND hwnd, UINT iMsg, WPARAM wParam, LPARAM lParam){	switch(iMsg)	{		case WM_DESTROY:			PostQuitMessage(0) ;					return 0 ;	}	return DefWindowProc(hwnd, iMsg, wParam, lParam) ;} 


tehre u go

This topic is closed to new replies.

Advertisement