[RESOLVED] Another Logic Question: Button Control Only To Fire Once.

[Morbane]

Well I have a Dialog with all kinds of things going on but for this question it regards a single Button Control. I would like the user to be able to use this button only once. It is pretty basic, but using a simple BOOL does not seem to do the trick - or at least how I have tried it.

My version:

//Reset Button
case IDC_BTN_RSTR:
{
     BOOL var = TRUE;
     if(var == FALSE) return TRUE;
     SetDlgItemInt(hwndDlg, IDC_STR, 0, FALSE);
     SetDlgItemInt(hwndDlg, IDC_STR_, 0, FALSE);
     SetDlgItemInt(hwndDlg, IDC_STR__, 0, FALSE);

     var = FALSE;
     return TRUE;
}

[VictorN]

My version:

//Reset Button
case IDC_BTN_RSTR:
{
     BOOL var = TRUE;
     if(var == FALSE) return TRUE;
...
}

Well, the line with if(var == FALSE) doesn't make any sense because above your set

BOOL var = TRUE;

If you set it to TRUE, then it is TRUE, so why check whether it is FALSE????

Why don't you want instead just to disable button after its first use?

[CrashPilot]

HRRRRrrmmmmmmmmmhhhhhhhhhhhhhh??? Whatever that code is supposed to do, rightnow it just returns TRUE and nothing else! Maybe you meant:

//Reset Button
case IDC_BTN_RSTR:
{
     static BOOL var = FALSE;
     if(var == FALSE)
     {
        SetDlgItemInt(hwndDlg, IDC_STR, 0, FALSE);
        SetDlgItemInt(hwndDlg, IDC_STR_, 0, FALSE);
        SetDlgItemInt(hwndDlg, IDC_STR__, 0, FALSE);
        var = TRUE;
        return TRUE;
     }
     else
     {
           return FALSE;
     }
}

However this will run once, there's no way to reset the oneshot button. Unles "var" becomes a publicly available variable may that be by declaring it public or some function to reset it again.
????????

[Morbane]

...So returning FALSE will make the button not reuseable? I imagined that was possible but was unsure about how doing so would effect the operation of the dialog.

I will see what that does.

Thanks for the help.

Edit: Great - a simple solution. I think I enjoy posting here too much - I will try to be more diligent before asking such simple questions.

[Igor Vartanov]

Great - a simple solution.

Simple, but not great. The button still looks active, but pressing it produces no effect: very, very bad solution. A button intended to be non-functional should be either disabled or hidden:

case IDC_BTN_RSTR:
{
        SetDlgItemInt(hwndDlg, IDC_STR, 0, FALSE);
        SetDlgItemInt(hwndDlg, IDC_STR_, 0, FALSE);
        SetDlgItemInt(hwndDlg, IDC_STR__, 0, FALSE);
        EnableWindow(GetDlgItem(hDlg, IDC_BTN_RSTR), FALSE);   // disable it
        //ShowWindow(GetDlgItem(hDlg, IDC_BTN_RSTR), SW_HIDE);   // or hide
        return TRUE;
}

[Morbane]

Thanks again Igor!

[RE-RESOLVED]

[CrashPilot]

Except that it wasn't intended as a solution but as a possible explanation on the behaviour he / she was looking for.

^^

--edit:

...So returning FALSE will make the button not reuseable? I imagined that was possible but was unsure about how doing so would effect the operation of the dialog.

No. Turning it false simply means that YOU will handle the the message and not the default handler:

 return DefWindowProc( hwnd, message, wparam, lparam );

.
Any message that you do not whish to handle should be defaulted back in that case. It's not realy a matter of enabling nor disabling funcionality.

In fact it would be better to return FALSE / NULL / 0 in both cases as you handle both cases.