<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#c9">Comment # 9</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=carlosg%40gnome.org" title="Carlos Garnacho <carlosg@gnome.org>"> Carlos Garnacho</a> <pre>Created <a href="attachment.cgi?id=319038&action=diff" name="attach_319038" title="wayland: add support for wl_pointer frame/axis_source/axis_discrete/axis_stop">attachment 319038</a> <a href="attachment.cgi?id=319038&action=edit" title="wayland: add support for wl_pointer frame/axis_source/axis_discrete/axis_stop">[details]</a> <a href='review?bug=756729&attachment=319038'>[review]</a> wayland: add support for wl_pointer frame/axis_source/axis_discrete/axis_stop This adds support for the new wl_pointer events available in v5. The wl_pointer.axis_source events can be ignored for the purposes here, the main reason they exist is so that the combination of axis_source=finger and axis_stop triggers kinetic scrolling. We don't need to care about the source, axis_stop is enough for us to tell us when we're scrolling. The wl_pointer.frame events group events together and is intended as a mechanism to coalesce events together. This for example allows us to now send a single GTK scroll event for a diagonal scroll. Previously, the two wl_pointer.axis events had to be handled separately. The wl_pointer.axis_discrete event sends mouse wheel clicks where appropriate, and is translated into up/down/left/right scroll events.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> </ul> </body> </html>