[Octave-bug-tracker] [bug #37359] Gui frozen at start

[Michael Godfrey]

Follow-up Comment #2, bug #37359 (project octave):

This suggests the need for an Octave
command argument in the --no-xxx family,
something like --no-qt-settings

But, also a more robust handling of
the qt-settings file would help as
well as:

1. Is the current handling correct if multiple
   instances are using the same qt-settings file?

2. Should there be a way of creating and using a
   designated q-settings file?

3. Is there a need for a "reset_qt_settings" function?

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?37359>

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