Chris,
I was reading your message watch code ... which raises obvious questions.
Do you know why some do, or some don't, go through the message loop?
I haven't used the loop in an app yet - the Callback functions have covered my needs so far - but I've been wondering what the advantage was of the loop for those of us who are programming mostly in DDT? From your post, apparently neither is a complete solution.
With what reading I've done so far, I'd have thought all messages would be captured by the loop - but apparently not. Don't I recall reading in Petzold's book that some messages don't go to a dialog at all - neither to the loop nor to the callback function? But I don't think he documented those which are not received by a dialog, nor do I find it in MSDN.
So how does a person guarantee that all messages can be received? Are SDK windows the only way to ensure access to all messages?
Thanks for the code you posted. I'll give it a try.
I was reading your message watch code ... which raises obvious questions.
Do you know why some do, or some don't, go through the message loop?
I haven't used the loop in an app yet - the Callback functions have covered my needs so far - but I've been wondering what the advantage was of the loop for those of us who are programming mostly in DDT? From your post, apparently neither is a complete solution.
With what reading I've done so far, I'd have thought all messages would be captured by the loop - but apparently not. Don't I recall reading in Petzold's book that some messages don't go to a dialog at all - neither to the loop nor to the callback function? But I don't think he documented those which are not received by a dialog, nor do I find it in MSDN.
So how does a person guarantee that all messages can be received? Are SDK windows the only way to ensure access to all messages?
Thanks for the code you posted. I'll give it a try.
Comment