[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #53836] Clicking a QDockWidget tab in a stack
From: |
Dan Sebald |
Subject: |
[Octave-bug-tracker] [bug #53836] Clicking a QDockWidget tab in a stack does not activate the associated widget |
Date: |
Fri, 4 May 2018 14:08:40 -0400 (EDT) |
User-agent: |
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:59.0) Gecko/20100101 Firefox/59.0 |
URL:
<http://savannah.gnu.org/bugs/?53836>
Summary: Clicking a QDockWidget tab in a stack does not
activate the associated widget
Project: GNU Octave
Submitted by: sebald
Submitted on: Fri 04 May 2018 06:08:38 PM UTC
Category: GUI
Severity: 3 - Normal
Priority: 5 - Normal
Item Group: Unexpected Error
Status: None
Assigned to: None
Originator Name:
Originator Email:
Open/Closed: Open
Discussion Lock: Any
Release: dev
Operating System: Any
_______________________________________________________
Details:
A very minor detail, but if there is a tab stack in the main GUI or in the
variable editor mouse button press on the tab of the visible panel in the
stack does not bring that item into focus. Attached are a couple screen shots
which show that nothing happens when I pressed the mouse button right where
the mouse cursor is shown. That is, I tried to activate the Command Window by
clicking the visible tab...nothing happened; focus did not transfer to the
Command Window. Of course, had I moved the cursor up and clicked in the
actual Command Window, then focus would change. Note that if the item in the
tab stack is not the visible one then clicking on that tab brings the item to
the front of the stack (i.e., visible) *and* gives it focus.
I'm attaching a second screenshot that illustrates the same thing happens with
the Variable Editor.
Either something related to main_window::focus_changed (QWidget *, QWidget
*new_widget) has to be changed, but I doubt that can be done because that slot
is connected directly to the qApp signal that indicates somewhere focus has
changed.
Instead, it looks like something in the label_dock_widget, which is a base
class of both octave_dock_widget and variable_dock_widget, has to be changed.
Either it could be something having to do with focus proxy, or perhaps one
will have to write a short mouse-press event handler for the tab buttons and
change focus even when the top stack tab is pressed.
_______________________________________________________
File Attachments:
-------------------------------------------------------
Date: Fri 04 May 2018 06:08:38 PM UTC Name:
gui_main_tab_not_activate_Screenshot_20180504_125238.png Size: 205KiB By:
sebald
<http://savannah.gnu.org/bugs/download.php?file_id=44093>
-------------------------------------------------------
Date: Fri 04 May 2018 06:08:38 PM UTC Name:
variable_editor_tab_not_activate_Screenshot_20180504_125351.png Size: 128KiB
By: sebald
<http://savannah.gnu.org/bugs/download.php?file_id=44094>
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?53836>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
- [Octave-bug-tracker] [bug #53836] Clicking a QDockWidget tab in a stack does not activate the associated widget,
Dan Sebald <=