I'm creating a dialog using CreateDialog() and running it as a modeless
dialog.
The documentation for IsDialogMessage() claims that a message should not
be further processed (translate/dispatch) if IsDialogMessage() returns TRUE.
However, I have found that the dialog will lock up if you click in the
title bar of it, unless you actually let some kinds of messages through
to translate/dispatch even though IsDialogMessage() returns TRUE:
case WM_NCLBUTTONDOWN:
case WM_NCMOUSEMOVE:
case WM_NCLBUTTONUP:
case WM_LBUTTONUP:
case WM_MOUSEMOVE:
This doesn't appear to be documented behavior, but seems to work OK.
Does anyone know if this is the appropriate thing to do? Are there other
messages I should let through to translate/dispatch as well?
(My dialog proc returns FALSE for pretty much everything except
WM_COMMAND, WM_INITDIALOG and WM_DESTROY).
Cheers,
/ h+
|
