Re: CreateDialog and sending a WM_NOTIFY from it

Udo,

>> dialog window *doesn't* seem to have a "window ID" that can be set.
>
> GWL_ID   Sets a new identifier of the child window. The window cannot be
>  a top-level window.
> The words are clear.

Yep.  I assumed that as I could read from it I could write it too and didn't 
read the docs for "Set" .   I was wrong. :-|

Though with that question I was thinking of "will changing it possibly 
disrupt the functioning of that (sub-)dialog".

> If I would inform the parent or owner of a dialog, I would call a function 
> of
> the object bound to its window handle,

You mean "objects" as one with methods, getters and setters ?    I'm not 
sure what that "bound to" would look like.   But no, my main dialog is of 
the common garden variety.

> or send or post an own message, a registered one,

I have thought about the latter, but considered it to be more cumbersome 
than that it would be helpfull.  Both the sub-dialog and its parent 
program/dialog its created by would need to do that* - and tear down 
ofcourse, as its global (and I, only need it local).

*pointing to the very same string! :-)

I also considered the first one, to pick a few "random" messageID values, 
and hope they do not overlap an already existing one.

Thats why I thought of using a notification message and the resource-ID I 
hoped my dialog would have stored somewhere.

> or call a given call-back-function.

Possible too.  But than I have to make sure that that async call-back 
doesn't clash with the rest of the program (having the message-loop 
sequentialize all actions makes ones live easier)...

And I have to ask : is there a technical reason why I shouldn't use the 
NM_NOTIFY message this way ?

Regards,
Rudy Wieser