On Sun, Mar 22, 2015 at 8:57 PM, Jonas Ådahl wrote:
> On Mon, Mar 23, 2015 at 01:21:38PM +1000, Peter Hutterer wrote:
>> On Mon, Mar 23, 2015 at 10:23:18AM +0800, Jonas Ådahl wrote:
>> > On Mon, Mar 09, 2015 at 01:28:04PM +1000, Peter Hutterer wrote:
>> > > The axis source determines how an event
On Mon, Mar 23, 2015 at 01:21:38PM +1000, Peter Hutterer wrote:
> On Mon, Mar 23, 2015 at 10:23:18AM +0800, Jonas Ådahl wrote:
> > On Mon, Mar 09, 2015 at 01:28:04PM +1000, Peter Hutterer wrote:
> > > The axis source determines how an event was generated. That enables
> > > clients to
> > > judge
On Mon, Mar 23, 2015 at 10:23:18AM +0800, Jonas Ådahl wrote:
> On Mon, Mar 09, 2015 at 01:28:04PM +1000, Peter Hutterer wrote:
> > The axis source determines how an event was generated. That enables clients
> > to
> > judge when to use kinetic scrolling.
>
> Nice to see this happening!
>
> I hav
On Mon, Mar 09, 2015 at 01:28:04PM +1000, Peter Hutterer wrote:
> The axis source determines how an event was generated. That enables clients to
> judge when to use kinetic scrolling.
Nice to see this happening!
I have not looked at the implementation so far, only the protocol. I have
some commen
The axis source determines how an event was generated. That enables clients to
judge when to use kinetic scrolling.
We can't extend the existing wl_pointer.axis events so instead this new event
is prefixed before each wl_pointer.axis event, i.e. the sequence becomes:
wl_pointer.axis_source
wl_poi
