XPost: alt.windows7.general, comp.os.ms-windows.programmer.win32   
   From: address@is.invalid   
      
   Newyana2,   
      
   > 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 would say I was right, I just didn't fare blindly on anyones word.   
   Especially not when I have not seen any info either way.   
      
   But do notice that the phrasing of the above is a bit vague: the "send ...   
   to its parent window" can mean what I'm doing (from one top-level dialog to   
   another), but as easily just that the control is talking to the window it is   
   placed on.   
      
   > I'm not sure I've ever used that message. The only code I   
   > can think of where it appears is with a RichEdit.   
      
   Most, if not all of the controls that are in the ComCtl32.DLL use   
   notification messages.   List- and treeview, list- and combobox, you name   
   it.  Heck, I could even say that a simple button sends a notification (in   
   the form of a WM_COMMAND) to its parent.   
      
   > The RichEdit sends the WM_NOTIFY to the parent window, as MS says.   
      
   The difference is that I'm sending messages from one top-level dialog to   
   another.  Yes, the first is owned by the other, but its still quite a   
   difference.   
      
   > Since you haven't explained exactly what you're trying to accomplish, this   
   > is all academic.   
      
   I Think I explained it in full in my first post: I want/need to get the   
   "window ID" of a(n owned) dialog (the IDD_SETTINGS one that was used as an   
   argument to CreateDialog).  Thats all.  No more, no less.   
      
   So no, there is nothing academic about it ... unless you are trying to "meta   
   problem" the whole thing - which is not something I'm willing to participate   
   in.   
      
   Any talk about *the example* of what I currently wanted to use it for is, to   
   me, wasted time.  You see, that notification already works (before I posted   
   my question here), even thoughI had to hard-code the "window ID".   
      
   Regards,   
   Rudy Wieser   
      
   p.s.   
   Adding the WS_CHILD attribute (with or without the DS_CONTROL attribute) to   
   the owned dialog doesn't make it return a "window ID" (GWL_ID), but does   
   allow me to set one - on the cost of the dialog becoming a control onto of   
   the parent - which is not at all what I need the owned dialog for. :-\   
      
   --- SoupGate-DOS v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)