https://bugs.kde.org/show_bug.cgi?id=500978

Friedrich W. H. Kossebau <kosse...@kde.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|general                     |wayland-generic
            Version|unspecified                 |6.3.2
           Assignee|kosse...@kde.org            |kwin-bugs-n...@kde.org
            Product|okteta                      |kwin

--- Comment #5 from Friedrich W. H. Kossebau <kosse...@kde.org> ---
(In reply to Zamundaaa from comment #3)
> One thing you can check is that the menu has the proper widget parent 

This here is about menus part of the main menu bar menus tree. Those submenus
are QMenus queried from QAction entries in QMenus plugged into QMenuBar.  I
guess the popup is controlled by QMenu::internalDelayedPopup(), and there the
menu widget relation internally seems to be trracked by
"d->activeMenu->d_func()->causedPopup.widget = this;".

Many, if not all, of the submenus which seem affected by what people had
observed are provided by KSelectAction. That one creates an internal QMenu
instance, which it sets to itself via QAction::setMenu(). So there is no widget
parent to this menu instance by default. And those QMenu instances will be
accessed from QMenu containers which have those actions as entries, as by above
referenced QMenu::internalDelayedPopup().
More precisely, the KSelectAction instances themselves are added to the
QMainWindow's QMenuBar in one of the QMenu instances as created by KXmlGui's
logic in Okteta's case. The KSelectionActions are owned by internal QObject
instances, possibly not reachable from QMainWindow object child tree, so only
lent into the menu's manifests.

I connected to the QMenu::aboutToShow signal, and parentWidget is a nullptr at
the time.

KWin developers, would you know any data bits to set to help the heuristics you
mentioned? 

Given the added observation "happens exactly when one popup should be shown
while another one is still open" I suspect though perhaps some data lookup
fails somewhere on the client or server side of the wayland protocols?

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to