entering wndprocess

When debugging, and i come cross a line such as

UpdateWindow (hwnd) ;

which will send a paint message, when debugging, even if i press f11 (step into), debug, does not go into wndprocess. Is there a way of debugging where it also steps through the cases in wndprocess when their called?

the only way i can do it, is if i place a breakpoint on the first line of code of each case, such as WM_PAINT etc. Which works ok, but when it comes to the end of that particualr case, and should then jump back to the function that called it, a debugg error complains of their being no source code to return to?
[625 byte] By [wheelie] at [2007-11-20 8:22:21]
# 1 Re: entering wndprocess
That is because the UpdateWindow and such are implemented in windows dlls and there is no source code for those for you to look at. Hence, it can show only assembly code
kirants at 2007-11-9 13:30:17 >
# 2 Re: entering wndprocess
ok, that makes sence,

well im just going through random code to see if the cases that i have in my wndprocess are called when i think their called, is their any way of doing this,

other than writing a message box in each one,

(messageboxes get annoying very quickly...)
wheelie at 2007-11-9 13:31:18 >