Re: [PATCH libinput 1/2] Change axis events to carry all directions

Hi, On 05-01-15 06:20, Peter Hutterer wrote: Sending separate axis events instead of one unified events is limiting, especially when simultaneously scrolling in both directions and the caller tries to implement kinetic scrolling. Take a page from the tablet-support branch and instead implement

[PATCH libinput 1/2] Change axis events to carry all directions

Sending separate axis events instead of one unified events is limiting, especially when simultaneously scrolling in both directions and the caller tries to implement kinetic scrolling. Take a page from the tablet-support branch and instead implement the axis event as a generic event that can conta