[PATCH RFC inputproto] Use flags for smooth scrolling, not axis labels.

[Daniel Stone]

On Mon, Aug 15, 2011 at 09:40:55PM +1000, Peter Hutterer wrote:
> On 15/08/11 21:09 , Daniel Stone wrote:
> >On Mon, Aug 15, 2011 at 03:28:03PM +1000, Peter Hutterer wrote:
> >>+The behavior of the server if there is more than one VertScroll or more than
> >>+one HorizScroll axes on the same device is undefined.
> >
> >Hmm, howso?
> 
> if you have two VertScroll axes, which one do you emulate button
> press events on? I bet in our implementation it'll just be the first
> one, but do we need to force this in the protocol? or just claim
> it's implementation-defined?
> 
> it only affects emulation, I agree that needs to be clarified better.

Well, for that it's now even easier to do emulation as we have the
is_scroll flag rather than comparing names, so it's actually fairly easy
to do axis -> button emulation from all axes.  The choice of axis to do
button -> axis emulation for would have to be implementation-defined
though, yeah -- good catch.

Cheers,
Daniel