Re: [PATCH libinput 1/2] Change the scroll step distance to 15 and document it as degrees

2015-01-19 Thread Peter Hutterer
On Mon, Jan 19, 2015 at 05:49:36PM -0800, Bill Spitzak wrote: > I really find it doubtful that users are thinking about how many times the > scroll wheel has revolved about it's axis! Much more likely is the tangent > distance that the edge of the scroll wheel has moved. > > On a really typical mo

Re: [PATCH libinput 1/2] Change the scroll step distance to 15 and document it as degrees

2015-01-19 Thread Bill Spitzak
I really find it doubtful that users are thinking about how many times the scroll wheel has revolved about it's axis! Much more likely is the tangent distance that the edge of the scroll wheel has moved. On a really typical mouse that I have it seems to be about 2.5mm per click. Looking at it

Re: [PATCH libinput 1/2] Change the scroll step distance to 15 and document it as degrees

2015-01-11 Thread Peter Hutterer
On Mon, Jan 12, 2015 at 09:37:05AM +0800, Jonas Ådahl wrote: > On Mon, Jan 12, 2015 at 09:12:35AM +1000, Peter Hutterer wrote: > > Similar to the mouse resolution, let's make the scroll distance a sensible > > predictable value. Most mice use a 15 degree angle per scroll click, so > > let's > > ch

Re: [PATCH libinput 1/2] Change the scroll step distance to 15 and document it as degrees

2015-01-11 Thread Jonas Ådahl
On Mon, Jan 12, 2015 at 09:12:35AM +1000, Peter Hutterer wrote: > Similar to the mouse resolution, let's make the scroll distance a sensible > predictable value. Most mice use a 15 degree angle per scroll click, so let's > change to that. This will alter behaviour in clients that expect 10 but it >

[PATCH libinput 1/2] Change the scroll step distance to 15 and document it as degrees

2015-01-11 Thread Peter Hutterer
Similar to the mouse resolution, let's make the scroll distance a sensible predictable value. Most mice use a 15 degree angle per scroll click, so let's change to that. This will alter behaviour in clients that expect 10 but it shouldn't be too bad. We return doubles anyway for the axis value, so t