I’m trying to use msgbox, warndlg, errordlg, or helpdlg to warn users that they have chosen an option from the main menu that has no data loaded for that particular option.
h=warndlg(["Solar data not loaded for - " yearmon],“chooseplotSOLARday”);
The box opens, and the message at title are correct, but execution immediately continues and the main menu (a listdlg) is redrawn on top of the msgbox.
Going back to the msgbox and clicking OK does nothing. The dialog stays on screen until a valid main menu selection is made. If I try and use the “modal” option, then it locks up and I have to kill octave with Task Manager.
The only dlg function that works as expected is questdlg, which halts execution and awaits a response before returning to the main menu.
h=questdlg(["Solar data not loaded for - " yearmon],“chooseplotSOLARday”,“OK”,“Got It”,“OK”);
One thing I noticed is that all the problem functions appear in a “java-esque” format while questdlg looks more like an OS dialog. Pictures attached.
Is it reasonable for me to expect msgbox and the others to halt execution until the user responds with OK? Even so, the OK is not working, so I currently cannot use them.
I’m running Octave 5.2.0 X86_64-w64-mingw32 on a windows 10 machine build 19041.867