I don't want [Enter] to close my dialog

[Drewpee]

Hi,

I'm writing a dialog based app (multithreaded, db accessing). And I realised that when you press enter, the windows message pump sends an IDOK response causing windows to end the modal loop. This would be ok if I wanted to shut down the app this way, but I don't have code in place to cleanup here and I don't want the program to exit on pressing [Enter].
So far, I wrote:

void CMyDlg::OnOK()
{
return;
}

to override the OnOK message and do nothing. It works but I'm not sure if it's the best way to do this. Would it be better, or is there a way to intercept the IDOK message/disable the message or something? Thanks for any/all help.

[ski6ski]

You could set focus to a different control.
Or you could remove the OnOK(); from the button.

Usualy I comment the OnOK(); out like this: //OnOK();
That usualy works.

[Drewpee]

Thanks ski6ski,

I did try removing the button, but MFC (I think) still processes the message, even when I took OnOK() out of the message map. Kind of a pain, thats why I wanted to intercept the message rather that override it.
Just after I posted, I found this on codeguru.com:

>>
Unfortunately, when the user press
Enter, the sheet still closes. To avoid this, do
not just hide the control but also disable it.

So the complete code will be:

CWnd * pButton = GetDlgItem(IDOK);
pButton->ShowWindow(FALSE);
pButton->EnableWindow(FALSE);
>>

But I still have to put the button somewhere on the dialog (its hidden at runtime).
Anyways, thanks for your help.

Corrollary:
Is there onything else (besides pressing [Enter] or the OK button) that will pass an IDOK response?

[jinx]

Right click on your edit control. Goto to the Styles tab, I think... Then check the Want Return option. If its not there, then goto another tab until u find it.

[ski6ski]

Oh yeah i forgot about that. Good idea jinx.

[nvoigt]

If you don't want [Return] to end your dialog, you probably don't
want [ESC] to cancel it either....

[Drewpee]

Thanks guys,

>If you don't want [Return] to end your dialog, you probably don't want [ESC] to cancel it either....>

You're right nv, but I actully handle that one becaue I have a cancel button that the user can press to abort a process. This is important because the dialog starts a long process that if the user changes his mind and doesn't want to do it any more, I have to clean up what was done. Pressing [ESC] actually passes an IDCANCEL message the same as the cancel button.

I ended up disabling the button and making it invisible in the code. The app has been running for 5 days now with no ill effects.

Thanks again

[zMan]

try to remove focus as you may to remove the focus from the IDOK.... it is a weird button... what I normally do is hide it, disable it... and create a different button... say submit or something then
I call the CDialog::OnOK(); from there...


something like this...

void CMyDlg::OnSubmit()
{

if( AllDataIsValid() )
CDialog::OnOK();
else
WarnUser();
}

the new button will not have the default focus like the OK button...