Forums before death by AOL, social media and spammers... "We can't have nice things"
|    alt.comp.os.windows-xp    |    Actually wasn't too bad for a M$-OS    |    17,273 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 16,988 of 17,273    |
|    R.Wieser to All    |
|    Re: CreateDialog and sending a WM_NOTIFY    |
|    17 Nov 24 08:26:04    |
      XPost: alt.windows7.general, comp.os.ms-windows.programmer.win32       From: address@is.invalid              Woodrow,              > The WM_NOTIFY message is for a control on a dialog to send to the dialog.       > Not for a dialog to send to its parent.              Do you have some (preferrably MS origionated) documentation to support that       ?              The dialog in question is, for all intents and purposes, a child of the       dialog that created it (they share the same message-loop).              > If your settings dialog is a control on another dialog, it must have       > the styles WS_CHILD and DS_CONTROL. Only then can it have a control ID.              Thank you. But no, its not.              I remember having read something about a "control parent" in relation to a       tab control. Never used it that way though.              > If your settings dialog is not a control on another dialog, you are       > misusing the WM_NOTIFY message. You will be on your own.              You see a problem. I don't. If you could explain that problem I would be       much obliged (it would give me a chance not to stumble into it).              Maybe you're thinking of sending such messages (containing pointers to data)       to another process ?              Regards,       Rudy Wieser.              --- SoupGate-DOS v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca