Finding My Own Errors

[shankle]

One of the most difficult and frustrating things I have experienced over the years
is finding my own errors. Ex:
        sequence of event in a Windows program:
          wm_create, wm_char,wm_lbuttondown, wm_keydown, wm_size etc......
          I coded wm_create to go to wm_char and wm_char to go to wm_size ....
    This error cost me a week in degugging :redface:

Of course I understand you guys never have this problem........

[dedndave]

we all do it - you're not alone   

it's nice to know the sequence of events when you create a window
i wrote this little program a few years back
it opens a "user mode" window first
then it opens a "presentation mode" window
both are essentially the same program - running in different modes
the messages received by the WndProc of the user mode window are sent to the presentation mode window to be displayed
so, some of the messages you see here are generated when the second window opens on top of the first

the hWin window is the user mode "frame" window
the hTxt window is a child window that consumes the entire client area