On Tue, Dec 30, 2014 at 05:19:45PM +, Daniel Stone wrote:
Hi,
On 29 December 2014 at 00:03, Peter Hutterer peter.hutte...@who-t.net
wrote:
On Sun, Dec 28, 2014 at 11:25:16PM +0100, Sjoerd Simons wrote:
The reason for not having any input devices could actually be that there
are
On Fri, Jan 02, 2015 at 02:22:04PM +0100, Sjoerd Simons wrote:
On Fri, 2015-01-02 at 13:07 +, Daniel Stone wrote:
Hi,
On 2 January 2015 at 12:24, Sjoerd Simons sjoerd.sim...@collabora.co.uk
wrote:
Under the assumption that weston-launch is a tool for developers to
start
Peter Hutterer peter.hutte...@who-t.net writes:
Reviewed-by: Peter Hutterer peter.hutte...@who-t.net
Merged.
de89c6b..3573855 master - master
--
-keith
signature.asc
Description: PGP signature
___
wayland-devel mailing list
Right now we only have two (scroll) axes and we could easily just check both
for non-zero values. If we want to allow further axes in the future, we need
a check whether an axis is set in an event.
We also need the mask to notify of a scroll stop event, which could otherwise
be confused as a
Sending separate axis events instead of one unified events is limiting,
especially when simultaneously scrolling in both directions and the caller
tries to implement kinetic scrolling.
Take a page from the tablet-support branch and instead implement the axis
event as a generic event that can
