https://bugs.kde.org/show_bug.cgi?id=436473
Fabian Vogt <fab...@ritter-vogt.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas
|ma/breeze/commit/f99b7ef621 |ma/breeze/commit/40d558e96d
|c9c69544158d245699fd8104db6 |607419b9bfaa9a706621a906bab
|753 |3e9
--- Comment #30 from Fabian Vogt <fab...@ritter-vogt.de> ---
Git commit 40d558e96d607419b9bfaa9a706621a906bab3e9 by Fabian Vogt.
Committed on 18/05/2021 at 10:14.
Pushed by fvogt into branch 'Plasma/5.22'.
Fix informing the underlying widget when leaving SplitterProxy
While the SplitterProxy is active, it intercepts all relevant events, so that
the underlying widget still thinks it's in the same "on splitter" state. When
the SplitterProxy is left, the underlying widget is sent a HoverLeave/HoverMove
event to make it aware of the new current cursor position. Without this, it
doesn't know that it's not supposed to be in the "on splitter" state, and when
it regains focus it just re-activates the SplitterProxy at the current cursor
position.
This was broken by accident in d201a1f187 ("Fix SplitterProxy not clearing
when above another QSplitterHandle"), which moved the hide() call past the
call to QCoreApplication::sendEvent. Previously that made isVisible() false,
which also prevented the interception of the HoverLeave/HoverMove events.
(cherry picked from commit f99b7ef621c9c69544158d245699fd8104db6753)
M +7 -4 kstyle/breezesplitterproxy.cpp
https://invent.kde.org/plasma/breeze/commit/40d558e96d607419b9bfaa9a706621a906bab3e9
--
You are receiving this mail because:
You are watching all bug changes.
