Skip to content
Snippets Groups Projects
Commit a9297211 authored by Rob Swindell's avatar Rob Swindell :speech_balloon:
Browse files

Fix bug with fixed event toggles

I'm totally perplexed that none of the compilers we have warned about this
obvious incorrect usage of the toggle_flag() function. Not warning about
passing false (0/NULL) for a char* makes some sense, but not the passing of
a const char* in place of a bool (int)? Maybe we should be building with
-Wall?
parent f9f1a16a
No related branches found
No related tags found
No related merge requests found
Pipeline #8111 passed
......@@ -341,10 +341,10 @@ void fevent_cfg(const char* name, fevent_t* event, const char* help)
uifc.changes = TRUE;
break;
case 1:
toggle_flag(native_opt, &event->misc, EX_NATIVE, native_help, false);
toggle_flag(native_opt, &event->misc, EX_NATIVE, false, native_help);
break;
case 2:
toggle_flag(use_shell_prompt, &event->misc, EX_SH, use_shell_help, false);
toggle_flag(use_shell_prompt, &event->misc, EX_SH, false, use_shell_help);
break;
case 3:
uifc.input(WIN_MID | WIN_SAV, 0, 0, "Command"
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment