Simple Windows message question.

PlayGGY · 2003-11-30T14:43:50

I have a WindowsEngine class, with WndProc outside of it (so it is unfortunately global). Well, I want to handle messages outside of WndProc and in the class, so I set up my own message handling function. The weird thing is, after I translate the message, and check the "message" component of it for WM_CLOSE, for example, it never ever registers that the message is WM_CLOSE. Right after I check, I send the very same message to WndProc with DispatchMessage, and it does register the message to be WM_CLOSE. I use OutputDebugString to see if it was received. This is where I check for the message... void CWindowsEngine::HandleInternals() { if (m_Status == ES_OK) { MSG WindowsMsg; while (PeekMessage(&WindowsMsg, NULL, 0, 0, PM_REMOVE)) { TranslateMessage(&WindowsMsg); switch (WindowsMsg.message) { case WM_CLOSE: { OutputDebugString("*****WM_CLOSE received in HandleInternals*****\n"); } case WM_DESTROY: { OutputDebugString("*****WM_DESTROY received in HandleInternals*****\n"); } } DispatchMessage(&WindowsMsg); } } } And this is WndProc... long CALLBACK WndProc(HWND hWnd, unsigned int Message, WPARAM wParam, LPARAM lParam) { switch (Message) { case WM_CREATE: { return 0; } case WM_CLOSE: { OutputDebugString("*****WM_CLOSE received in WndProc*****\n"); return 0; } case WM_DESTROY: { OutputDebugString("*****WM_CLOSE received in WndProc*****\n"); return 0; } default: { return DefWindowProc(hWnd, Message, wParam, lParam); } } } I hope the formatting isn''t messed up... I call WindowsEngine::HandleMessages every frame.

For Beginners

Started by PlayGGY November 29, 2003 01:20 PM

9 comments, last by PlayGGY 20 years, 4 months ago

PlayGGY

122

Author

November 30, 2003 11:10 AM

quote:Original post by Endurion
Some messages are sent internally by DefWindowProc and you wont see them in the message pump.

One way to get a WM_CLOSE is when the user clicks the X on the top right corner. In the pump you'll see only (guessing here: WM_NCLBUTTONDOWN/UP) which DefWindowProc will translate to WM_CLOSE and if that's not handled by you followed by WM_DESTROY and so on...

Oh... that explains it!

EDIT: OK, I don't expect any more replies now, but the message parameter of WndProc is WM_CLOSE, so it has its message identifier after it is "dispatched", while in WndProc, but outside of it. And, like I said, the LOWORD macro doesn't work.

I think I have a way around this, though, but it is pretty messy.

[edited by - PlayGGY on November 30, 2003 1:00:49 PM]

[edited by - PlayGGY on November 30, 2003 3:43:50 PM]

And the rockets' red glare, the bombs bursting in air,gave proof through the fight that our flag was still there.Oh say, does that star-spangled banner yet waveover the land of the free and the home of the brave?

Simple Windows message question.

This topic is closed to new replies.

Popular Topics

Recommended Tutorials

Simple Windows message question.

This topic is closed to new replies.

Popular Topics

Recommended Tutorials

Reticulating splines