RE: Handling dialogs created without using templates

[Santosh Siddheshwar]

Hi,
  Yes attached is a sample which is pretty similar to what I described
below.
Regards
Santosh Siddheshwar
 <<GetParent.zip>>
> -----Original Message-----
> From:	Dmitry Timoshkov [SMTP:[e-mail]]
> Sent:	Tuesday, March 30, 2004 12:51 PM
> To:	Santosh Siddheshwar
> Cc:	[e-mail]
> Subject:	Re: Handling dialogs created without using templates
>
> "Santosh Siddheshwar"  wrote:
> > I have an application that creates dialogs without using any of the
>
> Win32
> > Dialog creation APIs. I find that a lot of the 
> > functionality in DEFDLG_Proc (DM_SETDEFID, DM_GETDEFID & WM_NEXTDLGCTL)
>
> is
> > unavailable for use with
> > dialogs created this way. This is because we allocate the DIALOGINFO
> > structure only in the dialog creation APIs. Dialogs
> > created without using these APIs have NULL DIALOGINFO structure. I also
>
> find
> > that allocating this structure and initializing 
> > the members of the structure will get around this problem. Does anyone
> > visualize any problems with this approach?
> > Also where would the best place to put such code?
>
> Do you have a small, self-contained sample code which demonstrates
> what you have described?
>
> -- 
> Dmitry.

*********************************************************************
Disclaimer: The information in this e-mail and any attachments is
confidential / privileged. It is intended solely for the addressee or
addressees. If you are not the addressee indicated in this message, you may
not copy or deliver this message to anyone. In such case, you should destroy
this message and kindly notify the sender by reply email. Please advise
immediately if you or your employer does not consent to Internet email for
messages of this kind.
*********************************************************************

Handling dialogs created without using templates

[Dmitry Timoshkov]

"Santosh Siddheshwar"  wrote:
> Yes attached is a sample which is pretty similar to what I described
> below.

Thanks. Now I see where the problem is. We have to hook dialog creation
code into common window creation code, something similar to what I've done
recently for MDI. Alexandre, are my thoughts correct?