Thread: my wndProc is out of scope

Originally Posted by Raison

I read it in a book that i should not call the window function directly (e.g. return mf->wndProc(hwnd,message,wParam,lParam); ) because

The book was talking about the WNDPROC which is static in your case. You aren't calling the static WNDPROC directly when you call the virtual one.

what the book was likely suggesting is...


lets say you want to tell a window that you want it to repaint. You think that you can call the window function with a WM_PAINT message but you can't because it wont work.

or maybe you want to do some processing that happens when the thing is sized, so you call it with a WM_SIZE message.

These are the things you shouldn't do. Don't call it directly.

As for inside of the static or global WndProc function itself, you can certainly call other functions. Your virtual wndProc is not a WNDPROC at all, but a method on the class. Therefore you can most definitely call it explicitly.

Originally Posted by Raison

ok thanks for helping me out so far. I still have alot of doubts:

You mean like if i want to resize the window using its wndProc. I should not call it explicitly, but instead i should use CallWindowProc?
But i tot i should use SendMessage in this case. Then when should i use CallWindowProc?

you won't be able to do it that way anyway, but its just an example. Just don't call it directly. don't worry too much about why. Windows just wants to be the only one to call it.

The real matter here is that your virtual wndProc is not a WNDPROC so you can call it. Change the name if you want it to be less confusing