<html> <head> <base href="https://bugzilla.gnome.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - No kinetic scrolling on Wayland" href="https://bugzilla.gnome.org/show_bug.cgi?id=756729#c5">Comment # 5</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - No kinetic scrolling on Wayland" href="https://bugzilla.gnome.org/show_bug.cgi?id=756729">bug 756729</a> from <a href="page.cgi?id=describeuser.html&login=peter.hutterer%40who-t.net" title="Peter Hutterer <peter.hutterer@who-t.net>"> Peter Hutterer</a> <pre>Created <a href="attachment.cgi?id=313787&action=diff" name="attach_313787" title="0002-wayland-add-gdk_event_is_scroll_stop_event.patch">attachment 313787</a> <a href="attachment.cgi?id=313787&action=edit" title="0002-wayland-add-gdk_event_is_scroll_stop_event.patch">[details]</a> <a href='review?bug=756729&attachment=313787'>[review]</a> 0002-wayland-add-gdk_event_is_scroll_stop_event.patch Add a new gdk_event_is_scroll_stop_event() to check if a scroll event should be used for kinetic scrolling. This is a draft, the upstream protocol isn't declared stable yet. Note that I'm still ignoring the axis source here - we could make this depending on the 'finger' source, but the 'continuous' source too may trigger kinetic scrolling. An example for continuous scrolling is middle-button scrolling - the scroll stop is triggered when the scroll button is released.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> </ul> </body> </html>