On Tue, Apr 07, 2015 at 01:19:24PM +1000, Peter Hutterer wrote:
On Fri, Mar 27, 2015 at 10:23:43AM +0800, Jonas Ådahl wrote:
snip
Follow up questions:
Do we expect to get axis_stop on both the horizontal and vertical axes,
and is the client supposed to trigger its kinetic scrolling
On Fri, Mar 27, 2015 at 10:23:43AM +0800, Jonas Ådahl wrote:
On Fri, Mar 27, 2015 at 11:04:42AM +1000, Peter Hutterer wrote:
On Wed, Mar 25, 2015 at 09:14:08AM +0800, Jonas Ådahl wrote:
On Wed, Mar 25, 2015 at 10:27:10AM +1000, Peter Hutterer wrote:
The axis_source event determines how
On Fri, Mar 27, 2015 at 11:04:42AM +1000, Peter Hutterer wrote:
On Wed, Mar 25, 2015 at 09:14:08AM +0800, Jonas Ådahl wrote:
On Wed, Mar 25, 2015 at 10:27:10AM +1000, Peter Hutterer wrote:
The axis_source event determines how an axis event was generated. This
enables
clients to judge
On Wed, Mar 25, 2015 at 09:14:08AM +0800, Jonas Ådahl wrote:
On Wed, Mar 25, 2015 at 10:27:10AM +1000, Peter Hutterer wrote:
The axis_source event determines how an axis event was generated. This
enables
clients to judge when to use kinetic scrolling.
The axis_stop event notifies a
On Tue, Mar 24, 2015 at 5:27 PM, Peter Hutterer
peter.hutte...@who-t.net wrote:
The axis_source event determines how an axis event was generated. This enables
clients to judge when to use kinetic scrolling.
The axis_stop event notifies a client about the termination of a scroll
sequence,
The axis_source event determines how an axis event was generated. This enables
clients to judge when to use kinetic scrolling.
The axis_stop event notifies a client about the termination of a scroll
sequence, likewise needed to calculate kinetic scrolling parameters.
The axis_discrete event
On Wed, Mar 25, 2015 at 10:27:10AM +1000, Peter Hutterer wrote:
The axis_source event determines how an axis event was generated. This enables
clients to judge when to use kinetic scrolling.
The axis_stop event notifies a client about the termination of a scroll
sequence, likewise needed to
On Mar 24, 2015 6:14 PM, Jonas Ådahl jad...@gmail.com wrote:
On Wed, Mar 25, 2015 at 10:27:10AM +1000, Peter Hutterer wrote:
The axis_source event determines how an axis event was generated. This
enables
clients to judge when to use kinetic scrolling.
The axis_stop event notifies a