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

[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 than
> +one valuator is marked with Preferred, this should be considered a driver
> +bug and the behaviour is implementation-dependent.

'... is marked with Preferred _for the same scroll direction_, this
should be ...'

Otherwise you can only emulate vertical _or_ horizontal scrolling -- not
both -- without clients thinking you've violated the spec.

Cheers,
Daniel