Hi, Thanks. Would you be able to share details of the changes you did for handling MDI windows? Regards Santosh
-----Original Message----- From: Dmitry Timoshkov [SMTP:dmitry@baikal.ru] Sent: Tuesday, March 30, 2004 7:40 PM To: Santosh Siddheshwar Cc: wine-devel@winehq.com Subject: Re: Handling dialogs created without using templates
"Santosh Siddheshwar" santosh.s@sonata-software.com 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?
-- 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. *********************************************************************
"Santosh Siddheshwar" santosh.s@sonata-software.com wrote:
Thanks. Would you be able to share details of the changes you did for handling MDI windows?
The patch is here: http://cvs.winehq.com/patch.py?id=10783
I think that (almost) all that needs to be done about the problem is to move most of the DIALOG_CreateIndirect to WM_CREATE handler in DefDlgProc, including setting of WIN_ISDIALOG, i.e. just slightly rearrange dialog initialization code.