octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #60750] Variable Editor changes docking state


From: John W. Eaton
Subject: [Octave-bug-tracker] [bug #60750] Variable Editor changes docking state when 'openvar'-ring a variable
Date: Wed, 9 Jun 2021 10:00:47 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0

Follow-up Comment #6, bug #60750 (project octave):

There is definitely some strange behavior with dock widgets since my recent
changes to allow them to be opened when Octave is running in command line
mode.

I admit I don't fully understand how parenting and docking interact.  It seems
we currently assume that if a dock widget has its parent set to the
main_window widget then it is docked and if its parent is nullptr, it is
floating.  But is that necessary?  Is it possible for a floating window to
have the main_window widget as a parent?

My aim for the behavior of these widgets with the new terminal widget is
described below (copied from comment #11 of bug #60646).

It should be possible to have the following sequence (the lines marked with ?
is the behavior that I would expect but might still be up for debate):

 * open a dockable widget from the command line
 * open the desktop from the command line
   ? any open dockable widgets should remain undocked
 * dock one of the widgets that was initially opened from the command line or
undock one that was originally opened (and docked) with the main desktop
window
 * close the desktop window and return to the command line
   ? any undocked widgets should remain open
   ? widgets that were originally opened at the command line but were docked
when the desktop were closed should be closed with the main desktop window

When restarting Octave in command line mode, no widgets are restored, even if
they were open during a previous command line session (maybe that could be
configurable, but not opening windows is the default behavior I would
expect).

When starting Octave in GUI mode, should the window configuration to be
restored from the last time the main window was closed (possibly when
returning to the Octave command line) or to the window configuration used in
the last "pure" GUI session.  I suppose it is simplest to just save the
configuration when the main window is closed and restore that when restarting
the main window, whether from a command line session or not. 

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?60750>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]