[ANNOUNCE] libinput 1.10.1

libinput 1.10.1 is now available. This release fixes three crashers, one during tapping, two on startup/resume when the device node or seat weren't assigned correctly. You're strongly advised to update just to get those fixes. Three fixes to the libinput measure* tools as well, they should now

Re: [PATCH] unstable: add xdg-session-management protocol

On 2018/2月/26 08:58, Mike Blumenkrantz wrote: > for a variety of cases it's desirable to have a method for negotiating > the restoration of previously-used states for a client's windows. this > helps for e.g., a compositor/client crashing (definitely not due to > bugs) or a backgrounded client

Re: [PATCH 1/2] xdg-shell: move maximized state difnition together

With typos corrected: Reviewed-By: Mike Blumenkrantz On Tue, Feb 27, 2018 at 8:23 AM Silvan Jegen wrote: > Hi > > One typo corrected below. > > On Tue, Feb 27, 2018 at 1:24 PM, wrote: > > From: Markus Ongyerth > > > >

Re: [PATCH 2/2] xdg-shell: Make sure wording reflects expectations

Hi, This seems like a reasonable direction for a change, though I would suggest a slightly different approach. For all cases where it reads "the compositor will respond by emitting", instead change to something like "if the compositor decides to apply this state change then it will respond by

[PATCH weston] build: honour libinput header location

From: Jan Engelhardt Add the respective CFLAGS to the build, otherwise the build will error out as seen below. src/libinput-seat.c:30:22: fatal error: libinput.h: No such file or directory [Emil Velikov: polish commit message] Signed-off-by: Emil Velikov

Re: [PATCH 1/2] xdg-shell: move maximized state difnition together

Hi One typo corrected below. On Tue, Feb 27, 2018 at 1:24 PM, wrote: > From: Markus Ongyerth > > The xdg-shell documentation had part of the maximized state render > implications in the `set_maximized` request documentation, not the > actual state. > This moves

Re: [PATCH wayland] connection: Print the content of arrays in closures

On Tue, 27 Feb 2018 12:39:59 + Daniel Stone wrote: > Hi, > > On 4 December 2017 at 08:08, Pekka Paalanen wrote: > > On Fri, 1 Dec 2017 17:08:15 + Daniel Stone > > wrote: > >> On 10 July 2017 at 19:28, Emmanuel Gil

Re: [PATCH wayland] connection: Print the content of arrays in closures

Hi, On 4 December 2017 at 08:08, Pekka Paalanen wrote: > On Fri, 1 Dec 2017 17:08:15 + Daniel Stone wrote: >> On 10 July 2017 at 19:28, Emmanuel Gil Peyrot >> wrote: >> > The current behaviour when WAYLAND_DEBUG is

[PATCH 1/2] xdg-shell: move maximized state difnition together

From: Markus Ongyerth The xdg-shell documentation had part of the maximized state render implications in the `set_maximized` request documentation, not the actual state. This moves the relevant lines into the state description. Signed-off-by: Markus Ongyerth ---

[PATCH 2/2] xdg-shell: Make sure wording reflects expectations

From: Markus Ongyerth The wording in xdg-shell `set_*` requests implies the compositor *will* react to requests. This would give clients the control over its state, while they should just be able to kindly ask for a state change. This makes sure the language reflects that and

[PATCH 0/2] Improve wording in xdg-shell

From: Markus Ongyerth Hi, this is a small patch series that pulls together the definition of the maximized state and slightly improves the wording in xdg-shell `set_*` requests to reflect the amount of control clients have. Cheers, ongy Markus Ongyerth (2): xdg-shell: move

Re: [PATCH weston 1/2 v3] compositor-drm: Add support for DRM lease

Hi Philipp, Pekka, On Thu, 2018-02-22 at 10:29 +0200, Pekka Paalanen wrote: > On Wed, 21 Feb 2018 17:16:07 +0100 > Philipp Zabel wrote: > > > Hi Marius, > > > > On Wed, 2018-02-21 at 16:49 +0200, Marius Vlad wrote: > > > Signed-off-by: Marius Vlad