On Fri, Jan 08, 2016 at 02:43:10PM +1000, Peter Hutterer wrote:
> ping - can we merge this now?
Just pushed the protocol patch:
2b236af..c5356e9 master -> master
If no one objects, I intend to push the weston implementation patches as
well within a couple of days. FWIW, the weston APIs are
On Fri, Jan 08, 2016 at 02:43:10PM +1000, Peter Hutterer wrote:
> ping - can we merge this now?
I think so. If no one objects I will land this tomorrow.
Jonas
>
> On Tue, Dec 08, 2015 at 11:11:07AM +1000, Peter Hutterer wrote:
> > The frame event groups separate pointer events together. The
ping - can we merge this now?
On Tue, Dec 08, 2015 at 11:11:07AM +1000, Peter Hutterer wrote:
> The frame event groups separate pointer events together. The primary use-case
> for this at the moment is diagonal scrolling - a vertical/horizontal scroll
> event can be grouped together to calculate
On Mon, Dec 7, 2015 at 5:11 PM, Peter Hutterer
wrote:
>
> +
> +
> + Describes the source types for axis events. This indicates to the
> + client how an axis event was physically generated; a client may
> + adjust the user interface
On Tue, Dec 08, 2015 at 12:08:29PM -0800, Bill Spitzak wrote:
> On Mon, Dec 7, 2015 at 5:11 PM, Peter Hutterer
> wrote:
>
> >
> > +
> > +
> > + Describes the source types for axis events. This indicates to the
> > + client how an axis event was
The frame event groups separate pointer events together. The primary use-case
for this at the moment is diagonal scrolling - a vertical/horizontal scroll
event can be grouped together to calculate the correct motion vector.
Frame events group all wl_pointer events. An example sequence of motion