[Octave-patch-tracker] [patch #7990] Add builtin Qt equivalents of UI dialogs, i.e., , qterrordlg, qtinputdlg, etc.

[Dan Sebald]

Follow-up Comment #3, patch #7990 (project octave):

Yes, this is why I didn't endeavor to start adding script files.

Another reason for the "is_gui_running" check inside the builtins is for when
someone tries calling the routines without the GUI present.  (Try the commands
launching with --no-gui.)

Well, there are a number of ways one could go.

1. A set of scripts for "errordlg", etc. that is installed particular to how
Octave is launched.

2. Or, here's an idea I like.  Recall I wondered if we could make the
"is_gui_running" test be more informative about which gui is running.  The
"errordlg" command and associates could be made very general in C++ code with
something like:

std::string guiname = is_gui_running ();
if guiname.empty ()
  error("must be running a GUI system for this command")
  return
else
  std::string function_name;
  function_name << guiname << "errordlg"
  call function_name
end

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/patch/?7990>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/