On Thu, Jun 04, 2015 at 01:49:26PM +0800, Jonas Ådahl wrote:
> On Thu, Jun 04, 2015 at 03:28:15PM +1000, Peter Hutterer wrote:
> > On Thu, Jun 04, 2015 at 01:09:06PM +0800, Jonas Ådahl wrote:
> > > On Thu, Jun 04, 2015 at 02:41:52PM +1000, Peter Hutterer wrote:
> > > > To group separate vertical/ho
On Thu, Jun 04, 2015 at 03:28:15PM +1000, Peter Hutterer wrote:
> On Thu, Jun 04, 2015 at 01:09:06PM +0800, Jonas Ådahl wrote:
> > On Thu, Jun 04, 2015 at 02:41:52PM +1000, Peter Hutterer wrote:
> > > To group separate vertical/horizontal scroll events together. Likewise it
> > > enables axis_stop
On Thu, Jun 04, 2015 at 01:09:06PM +0800, Jonas Ådahl wrote:
> On Thu, Jun 04, 2015 at 02:41:52PM +1000, Peter Hutterer wrote:
> > To group separate vertical/horizontal scroll events together. Likewise it
> > enables axis_stop events to be grouped so that the final vector for kinetic
> > scrolling
On Thu, Jun 04, 2015 at 02:41:52PM +1000, Peter Hutterer wrote:
> To group separate vertical/horizontal scroll events together. Likewise it
> enables axis_stop events to be grouped so that the final vector for kinetic
> scrolling may be calculated correctly.
>
> Multiple scroll sources within the
To group separate vertical/horizontal scroll events together. Likewise it
enables axis_stop events to be grouped so that the final vector for kinetic
scrolling may be calculated correctly.
Multiple scroll sources within the same frame is not expected, but the
protocol allows this use-case, i.e. ax
