[Octave-bug-tracker] [bug #53836] Clicking a QDockWidget tab in a stack does not activate the associated widget

[Dan Sebald]

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

I think there might be such a signal:

http://doc.qt.io/qt-5/qtabbar.html#signals

Probably tabBarClicked().  It might be difficult to get at in the QMainWindow
environment or it could involve a dynamic connection as these tab groups
appear.  For example, the following signal should be emitted when a widget is
docked or moved elsewhere

http://doc.qt.io/qt-5/qdockwidget.html#dockLocationChanged

Then one could check the tab stack it belongs to and make sure that tab stack
has tabBarClicked() connected to some new routine that will move the focus to
the parent window.  Most likely disconnect-then-reconnect so that connections
don't build up with each focus change.  Or something like that.  If a tab
stack disappears, it's connections should automatically go away.

Low priority, as it isn't too difficult clicking inside the content of the
QDockWidget.

    _______________________________________________________

Reply to this item at:

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

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