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,992 of 17,273    |
|    Newyana2 to R.Wieser    |
|    Re: CreateDialog and sending a WM_NOTIFY    |
|    17 Nov 24 09:34:45    |
      XPost: alt.windows7.general, comp.os.ms-windows.programmer.win32       From: newyana@invalid.nospam              On 11/17/2024 2:26 AM, R.Wieser wrote:              >> 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       > ?               You seem to be right: "Sent by a common control to its parent       window when an event has occurred in the control or the control       requires some kind of information." (MSDN)               I'm not sure I've ever used that message. The only code I       can think of where it appears is with a RichEdit. I have to       watch for WM_NOTIFY in the subclass of the parent window       in order to get the EN_SELCHANGE RichEdit event, to know       when the selection has changed. The RichEdit sends the       WM_NOTIFY to the parent window, as MS says.               Since you haven't explained exactly what you're trying       to accomplish, this is all academic. Without context and       details it sounds like you're trying to send messages within       your own program, like a son writing a letter to his mother       and sending it through the mail, when you could use something       like an event or function, since you're writing both the parent       window and the child window.              --- 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