https://bugs.kde.org/show_bug.cgi?id=363548
Kai Uwe Broulik <k...@privat.broulik.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |fa...@kde.org,
| |mgraess...@kde.org
--- Comment #10 from Kai Uwe Broulik <k...@privat.broulik.de> ---
This bug is so absurd. The bug does not happen if I don't pass a window to the
"new KRun" call in DolphinViewContainer.
It passes "this", ie. the DolphinViewContainer widget, which has status bar,
KUrlNavigator as well as the DolphinView (one of the affected QGraphicsViews).
I traced it down in KRun to KStartupInfo. If I remove the
KStartupInfo::sendChange(id, data); call in KRun the bug does not happen.
CC'ing David F (as KRun guru) and Martin G (as KWindowSystem guru) - I have no
idea how this happens. The docs for KStartupInfo say it's the "top level
widget", so perhaps it should be DolphinMainWindow (indeed, if for testing f I
pass KMainWindow::memberList().first()) and not the view container? I don't see
how this could end up keeping mouse events (stuff like "window became
(in)active" arrive fine) from the graphics views?! It even affects the places
sidebar which is *not* in the affects DolphinViewContainer but has its own
afaics.
--
You are receiving this mail because:
You are watching all bug changes.
