Re: [PATCH inputproto 2/2] Move scroll information into a new class.

2011-09-22 Thread Daniel Stone
Hi, On Mon, Aug 22, 2011 at 03:35:17PM +1000, Peter Hutterer wrote: +If more than one scroll valuator of the same type is present on a device, +the valuator marked with Preferred is used to convert legacy button events +into scroll valuator events. If no valuator is marked Preferred or more

Re: [PATCH inputproto 2/2] Move scroll information into a new class.

2011-09-22 Thread Peter Hutterer
On Thu, Sep 22, 2011 at 11:06:54AM +0100, Daniel Stone wrote: Hi, On Mon, Aug 22, 2011 at 03:35:17PM +1000, Peter Hutterer wrote: +If more than one scroll valuator of the same type is present on a device, +the valuator marked with Preferred is used to convert legacy button events +into

[PATCH inputproto 2/2] Move scroll information into a new class.

2011-08-21 Thread Peter Hutterer
Using labels only to mark smooth scrolling axes disallows scrolling from hardware events (e.g. a mouse wheel). If those axes are marked as scrolling axes instead, the clients lose information which hardware axis this event corresponds to. For example, on Wacom devices, the client can benefit from