Re: [PATCH v4] protocol: Extend wl_touch with touchpoint shape and orientation

2016-10-31 Thread Peter Hutterer
On Mon, Oct 31, 2016 at 01:02:32PM -0700, Dennis Kempin wrote: > This CL updates the wl_touch interface with a shape and > orientation event. > The shape/orientation of a touch point is not relevant for most UI > applications, but allows a better experience in some cases > such as drawing apps. >

Re: weston and graphics tablet support?

2016-10-31 Thread Jason Gerecke
On 10/27/2016 10:22 PM, Peter Hutterer wrote: > Time to discuss graphics tablet support in weston: I had a patchset for some > earlier version of the tablet protocol, since then we've added a few bits > and bobs, including the mode switching support. > > Short story behind this email is: I serious

Re: weston and graphics tablet support?

2016-10-31 Thread Peter Hutterer
On Mon, Oct 31, 2016 at 08:34:07PM +0100, Armin Krezović wrote: > On 30.10.2016 23:59, Peter Hutterer wrote: > > On Fri, Oct 28, 2016 at 12:32:00PM +0200, Armin Krezović wrote: > >> Hi > >> > >> On 28.10.2016 07:22, Peter Hutterer wrote: > >>> Time to discuss graphics tablet support in weston: I ha

Re: [PATCH v4] protocol: Extend wl_touch with touchpoint shape and orientation

2016-10-31 Thread Dennis Kempin
I never finished applying the suggestions from the previous reviews. Now that I am finally getting through my backlog of issues, I have fixed following: - Fixed indentation - Updated wording of frame and shape/orientation descriptions On Mon, Oct 31, 2016 at 1:02 PM, Dennis Kempin wrote: > This

Re: weston and graphics tablet support?

2016-10-31 Thread Armin Krezović
On 30.10.2016 23:59, Peter Hutterer wrote: > On Fri, Oct 28, 2016 at 12:32:00PM +0200, Armin Krezović wrote: >> Hi >> >> On 28.10.2016 07:22, Peter Hutterer wrote: >>> Time to discuss graphics tablet support in weston: I had a patchset for some >>> earlier version of the tablet protocol, since then

[PATCH weston] xwayland: Move includes to avoid deprecation warnings

2016-10-31 Thread Daniel Stone
compositor.h already helpfully defines WL_HIDE_DEPRECATED for us, so we don't get warnings about wl_buffer (in particular) being deprecated when we have wayland-server headers defining it as deprecated, and then wayland-client headers using the type. Move it to be before all our other includes, so

[PATCH wayland 1/1] protocol: Remove inconsistent line breaks

2016-10-31 Thread Yong Bakos
From: Yong Bakos Enum entries and message arguments are sometimes preceded by a blank line, but often aren't. Standardize the format of the protocol specification by removing blank lines preceding a list of message arguments and enum entries. Signed-off-by: Yong Bakos --- protocol/wayland.xml

[PATCH wayland 0/1] protocol: Remove inconsistent line breaks

2016-10-31 Thread Yong Bakos
From: Yong Bakos I know, "not another crazy line break patch!" Authors have been using line breaks before enum entries and argument elements inconsistently; this patch, and a separate one for wayland-protocols, removes the line breaks, making all declarations consistent. This patch represents t

[PATCH wayland-protocols 0/1] (multiple): Remove inconsistent line breaks

2016-10-31 Thread Yong Bakos
From: Yong Bakos I know, "not another crazy line break patch!" Authors have been using line breaks before enum entries and argument elements inconsistently; this patch, and a separate one for wayland.xml itself, removes the line breaks, making all declarations consistent. This patch represents

[PATCH wayland-protocols 1/1] (multiple): Remove inconsistent line breaks

2016-10-31 Thread Yong Bakos
From: Yong Bakos Enum entries and message arguments are sometimes preceded by a blank line, but often aren't. Standardize the format of the protocol specification by removing blank lines preceding a list of message arguments and enum entries. Signed-off-by: Yong Bakos --- stable/presentation-

Re: weston and graphics tablet support?

2016-10-31 Thread Daniel Stone
Hi, On 28 October 2016 at 06:22, Peter Hutterer wrote: > Short story behind this email is: I seriously question the point of having a > tablet implementation in weston. I know it's supposed to be the test bed for > protocols (fwiw, we already have mutter + GTK support for tablets). But in > order