[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [kwin] [Bug 393639] Mouse cursor flicker when passing window borders
From:       Martin Flöser <bugzilla_noreply () kde ! org>
Date:       2018-05-03 18:42:30
Message-ID: bug-393639-17878-rxZW3Yiw6U () http ! bugs ! kde ! org/
[Download RAW message or body]

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

--- Comment #22 from Martin Flöser <mgraesslin@kde.org> ---
We have here a sequence which I kind of expected:

[3931322,539] wl_pointer@15.enter(17, wl_surface@68, 622,000000, 2,000000)
[3931322,651]  -> wl_pointer@15.set_cursor(17, wl_surface@16, 4, 4)
[3931322,717]  -> wl_surface@16.attach(wl_buffer@50, 0, 0)
[3931322,757]  -> wl_surface@16.damage(0, 0, 32, 32)
[3931322,805]  -> wl_surface@16.commit()


Qt first sets the new cursor to surface 16, then attaches the buffer and
commits the surface. This could result in KWin resetting the cursor. KWin
reacts on the set_cursor call and if the surface has no buffer attached it will
update cursor to invalid. It looks like everything is save here, but it's a
potential risky area. I have to look up whether that's wrong in Qt or in KWin.

Anyway I did some more investigation and found another code path which could
result in resetting the cursor. I'll attach a patch on top of the other patch.

-- 
You are receiving this mail because:
You are watching all bug changes.=
[prev in list] [next in list] [prev in thread] [next in thread]