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

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

[Octave-bug-tracker] [bug #53046] Variable Editor: feature request to ma


From: Dan Sebald
Subject: [Octave-bug-tracker] [bug #53046] Variable Editor: feature request to make multiple tables visible at once.
Date: Sun, 18 Feb 2018 05:12:24 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:55.0) Gecko/20100101 Firefox/55.0

Follow-up Comment #31, bug #53046 (project octave):

Reply to comment #29:  I didn't test whether undocking unparents (I wouldn't
think it should not do that, but maybe it does).  It does create a new window,
at least from the window-system's perspective.  (QApplication::activeWindow()
should indicate what the top level window of the focused object is.)  Perhaps
there is a base-level object type to search for rather than
"octave_dock_widget *" that will catch both types.  I'd also say that having
everything connected to QApplication::focusChanged isn't a significant drain
on the system.  Changing focus isn't a high-rate type of operation on the
user's part, and there are much more computationally intensive operations,
relatively speaking, like drawing the window contents.

Reply to comment #30:  The reason for the intermediate label_dock_widget is to
give the same look-and-feel for that thin header in both the V.E. and in the
main GUI window (both octave_dock_widget and variable_dock_widget now inherit
label_dock_widget).  By maintaining a similar appearance and action it means
faster comprehension for the user.  And also to give access to the label that
is placed in that header so that its background color can be altered.  So, yes
in a way it is a natural way of doing this, more along the line of OOP
philosophy.  Otherwise, the variable_editor is doing all these things,
replicating the code that constructs the header needing to access the labels
either by some member function or keeping track of labels somewhere.

    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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