%BS_OWNERDRAW and Enter

[Semen Matusovski]

Guys --
a form has three buttons with id 115-117. Control Add are located in the same order (115..117).
Focus has id #115. If to use ordinary buttons, Enter generates WM_COMMAND with CbCtl = 115.
But if to add %BS_OWNERDRAW style, CbCtl = 117.

Something strange (I think in IsDialogMessage). How to bypass this behaviour by more or less "normal" way (w/o changes in message loop, subclassing ...) ?

------------------
E-MAIL: [email protected]

[Bern Ertl]

Hi Semen, I'm just guessing, but have you tried setting the focus
on the button (115?) that you want active with the enter key?

Perhaps the owner draw is changing the focus?!?



------------------
Bernard Ertl

[Semen Matusovski]

Bern --
Yes, 115 has focus (100% sure).
I read about IsDialogMessage and added to DlgProc

  Case %DM_GETDEFID ' = WM_USER
     Function = MakDwd(115, %DC_HASDEFID)

All is nice, except - now I can't understand why changing to Function = MakDwd(116, %DC_HASDEFID) doesn't make 116 as default (remains 115).



------------------
E-MAIL: [email protected]

[Bern Ertl]

Sorry I can't be of more help. I'm still learning this stuff.

Have you tried changing the ID of the 115 button to %IDOK, or
is that not an option?



------------------
Bernard Ertl

[Borje Hagsten]

Sounds like the dialog relates to last control created for ownerdrawn
style and first control created for standard style. Change order of
creation when using ownerdrawn controls?


------------------

[Semen Matusovski]

It seems to me I found a "normal", documented way (works at least, under Windows 2000)

Dialog Send CbHndl, %DM_SETDEFID, x, 0  (x = 115..117)

(w/o Case %DM_GETDEFID ...)

------------------
E-MAIL: [email protected]