FW: WM_NEXTDLGCTL changes the default button ID and does not rest ore default control identifier

[Alexandre Julliard]

Krishna Murthy <Krishna.Murthy at 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 at winehq.org