<html>
<head>
<base href="https://bugzilla.gnome.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Cursors for Wacom tablets are not always updated correctly under Wayland"
href="https://bugzilla.gnome.org/show_bug.cgi?id=785375#c6">Comment # 6</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Cursors for Wacom tablets are not always updated correctly under Wayland"
href="https://bugzilla.gnome.org/show_bug.cgi?id=785375">bug 785375</a>
from <span class="vcard"><a href="page.cgi?id=describeuser.html&login=carlosg%40gnome.org" title="Carlos Garnacho <carlosg@gnome.org>"> <span class="fn">Carlos Garnacho</span></a>
</span></b>
<pre>Created <span class=""><a href="attachment.cgi?id=356370&action=diff" name="attach_356370" title="gtklinkbutton: Set cursor on button's event window">attachment 356370</a> <a href="attachment.cgi?id=356370&action=edit" title="gtklinkbutton: Set cursor on button's event window">[details]</a></span> <a href='review?bug=785375&attachment=356370'>[review]</a>
gtklinkbutton: Set cursor on button's event window
Setting the cursor on the widget window (i.e. the parent widget's) is
finicky because the cursor needs to be updated on crossing events, and
will yield the wrong result for other master devices that happen to be
in other areas of the same parent widget's window.
Just set it always on the event window created by the GtkButton parent
class. That window was causing the crossing events, so the rectangle
that gets the hand cursor set will be the same size, and we don't need
to track pointer crossing state that way.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>