<html> <head> <base href="https://bugzilla.gnome.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - move animatable cursors' current frame info into GdkCursor" href="https://bugzilla.gnome.org/show_bug.cgi?id=735847#c3">Comment # 3</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - move animatable cursors' current frame info into GdkCursor" href="https://bugzilla.gnome.org/show_bug.cgi?id=735847">bug 735847</a> from <a href="page.cgi?id=describeuser.html&login=carlosg%40gnome.org" title="Carlos Garnacho <carlosg@gnome.org>"> Carlos Garnacho</a> <pre>Created <a href="attachment.cgi?id=316199&action=diff" name="attach_316199" title="wayland: Do not store the grab cursor separately">attachment 316199</a> <a href="attachment.cgi?id=316199&action=edit" title="wayland: Do not store the grab cursor separately">[details]</a> <a href='review?bug=735847&attachment=316199'>[review]</a> wayland: Do not store the grab cursor separately After the grab is finished, we would expect an enter event, and GDK updating internally the cursor for that window and device. This means there is no need at all to store it separately in the backend. As a side effect, animated cursors are now also possible on grab icons.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> </ul> </body> </html>