https://bugs.kde.org/show_bug.cgi?id=371229
Martin Gräßlin <mgraess...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|WAITINGFORINFO |INVALID
Status|NEEDSINFO |RESOLVED
--- Comment #4 from Martin Gräßlin <mgraess...@kde.org> ---
Well on X11 the window manager is not involved in that. The first drag is
handled inside the application - the second drag as well. For the second
application there is no chance to know what was going on.
In fact as far as I understand the problem from an X11 protocol point of view
everything seems fine. A pointer enter is supposed to be sent to the window
below the cursor as soon as the other window crashes. And the window then
reacts.
On Wayland the compositor has a little bit more choice, luckily:
case QEvent::MouseMove: {
if (event->buttons() == Qt::NoButton) {
// update pointer window only if no button is pressed
input()->pointer()->update();
}
--
You are receiving this mail because:
You are watching all bug changes.
