[Top][All Lists]

[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: Sat, 17 Feb 2018 03:57:17 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:55.0) Gecko/20100101 Firefox/55.0

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

I'll let you think about focus since you are working on that, but to reiterate
what I think you are saying is that rather than having everything hooked to
the one signal focusChanged(), there might be a sort of fanning out at each
level.  Such a thing could be done at the octave_dock_widget level, e.g.

focusChange -> octave_dock_widget_slot
if (octave_dock_widget is active)
  octave_dock_widget_signal -> variable_dock_widget

in which case all that needs to be done is change the connection of the

Again, I'll let you work out the general theme, but looking at some of the
code around that changeset, you might achieve some of that using already
existing Qt methods.  Have a look at something like this:

findChildren<octave_dock_widget *> (QString (), Qt::FindDirectChildrenOnly);

instead of

main_window::dock_widget_list (void)

(see http://doc.qt.io/qt-5/qobject.html#findChildren) and 

if (new_widget == focusWidget ())

instead of that code that looks at all the objects checking if they are
ancestors.  The QObject::focusWidget() effectively does that
(QObject::focusWidget() is not the same as the QApplication::focusWidget(),
see http://doc.qt.io/qt-5/qwidget.html#focusWidget)


Reply to this item at:


  Message sent via/by Savannah

reply via email to

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