Alexandre, I am resending this patch. There exists a defect 2388. Also confirmed that it fixes one of the Katia's defect found.
Please let us know about your thoughts. Thanks, Krishna -----Original Message----- From: Krishna Murthy Sent: Tuesday, June 22, 2004 2:56 PM To: 'Alexandre Julliard'; Krishna Murthy Cc: wine-devel@winehq.org Subject: RE: FW: WM_NEXTDLGCTL changes the default button ID and does not rest ore default control identifier
Alexandre, Please find attached modified patch. The method DEFDLG_SetDefButton() now accepts the BOOL bSetDefID parameter to adapt for both DM_SETDEFID and WM_NEXTDLGCTL.
Thanks, Krishna -----Original Message----- From: Alexandre Julliard [mailto:julliard@winehq.org] Sent: Friday, June 18, 2004 10:30 AM To: Krishna Murthy Cc: wine-devel@winehq.org Subject: Re: FW: WM_NEXTDLGCTL changes the default button ID and does not rest ore default control identifier
Krishna Murthy Krishna.Murthy@guptaworldwide.com writes:
No, it is required. The DEFDLG_SetDefButton() is also called from message DM_SETDEFID. In this case idResult should set to the default button ID passed. And the current logic of DEFDLG_SetDefButton() does what is required for DM_SETDEFID.
Well, of course you'd need to adapt the DM_SETDEFID handling to the change. I think that's better than sending duplicate messages.
-- Alexandre Julliard julliard@winehq.org