[ANNOUNCE] libinput 1.4.901

2016-09-06 Thread Peter Hutterer
The first RC for libinput 1.5 is available A large part of this development cycle was internal cleanups and improvements to the test suite, only few new features were added. For touchpads, we now have a new configuration option to allow a 1/2/3 finger tap be mapped to left, middle and right, res

[ANNOUNCE] weston 1.11.93

2016-09-06 Thread Bryce Harrington
This is the release candidate for weston 1.12. A few of the notable changes since 1.11 are summarized below. Weston's internal code has been restructured into a new software library, libweston. This is intended for use by other compositor efforts that want to more easily utilize Weston's interna

[ANNOUNCE] wayland 1.11.93

2016-09-06 Thread Bryce Harrington
This is the release candidate for Wayland 1.12. We're on schedule for the official release on Tuesday, September 13th. Here is a brief run-down of a few of the main changes since 1.11. The core protocol documentation has received numerous refinements to improve its clarity and consistency. Alon

[PATCH libinput] touchpad: require at least 3 events before enabling trackpoint palm detection

2016-09-06 Thread Peter Hutterer
Some trackpoints, notably the one on the Lenovo T460s have a tendency to send the odd event even when they're not actually used. Trackpoint events trigger palm detection (see 0210f1fee193) and thus effectively disable the touchpad, causing the touchpad to appear nonresponsive. Fix this by requirin

Re: [PATCH wayland] scanner: Standardize return annotation

2016-09-06 Thread Peter Hutterer
On Tue, Sep 06, 2016 at 06:36:20AM -0700, Yong Bakos wrote: > From: Yong Bakos > > All the doxygen annotations for return values use \return. > > Match this annotation with the existing convention. > > Signed-off-by: Yong Bakos > --- > src/scanner.c | 2 +- > 1 file changed, 1 insertion(+), 1

Re: [PATCH v2 libinput 6/6] tablet: add touch arbitration

2016-09-06 Thread Jason Gerecke
On 09/05/2016 06:04 PM, Peter Hutterer wrote: > So far we've relied on the wacom kernel module to do touch arbitration for us > but that won't be the case in upcoming kernels. Implement touch arbitration in > userspace by pairing the two devices and suspending the touch device whenever > a tool com

[PATCH wayland v4] util: Document wl_list methods

2016-09-06 Thread Yong Bakos
From: Yong Bakos Add doxygen comment blocks to all wl_list methods. Signed-off-by: Yong Bakos --- v4: Fix variable name in sample code. (pq) Remove implemenetation details of pointer state. (pq) Remove note about __typeof__ entirely. - it's not helpful as a note or a code comment ei

[PATCH wayland] scanner: Standardize return annotation

2016-09-06 Thread Yong Bakos
From: Yong Bakos All the doxygen annotations for return values use \return. Match this annotation with the existing convention. Signed-off-by: Yong Bakos --- src/scanner.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/scanner.c b/src/scanner.c index c927275..0a348e5

session management in wayland

2016-09-06 Thread zahlenmeer
Hi, I am curious how session management works in wayland? In X we have xsmp, but I couldn't find something similar for wayland. The documentation briefly touches session compositors, but I couldn't find out if there's a protocol defined or how basic session save/restore and other session manager ta

Re: [PATCH wayland] server: allow removing any wl_listener from a signal when emitted

2016-09-06 Thread Giulio Camuffo
Hi, Thanks for the great wrap-up! > > > A proposal > > I believe we could have a private and safe variant of wl_signal used > internally for all these. We would still use struct wl_listener as is, > and be completely ABI compatible. > > wl_signal would be left as is. If someone needs a w

Re: [PATCH wayland] server: allow removing any wl_listener from a signal when emitted

2016-09-06 Thread Pekka Paalanen
On Tue, 6 Sep 2016 10:06:16 +0300 Giulio Camuffo wrote: > wl_list_for_each_safe, which was used by wl_signal_emit is not really > safe. If a signal has two listeners, and the first one removes and > re-inits the second one, it would enter an infinite loop. > This commit adds a wl_list_iterate_sa

Re: [PATCH weston] libweston-desktop/xwayland: Do not over-destroy the view

2016-09-06 Thread Giulio Camuffo
2016-09-01 2:27 GMT+03:00 Quentin Glidic : > On 30/08/2016 02:26, Bryce Harrington wrote: >> >> On Thu, Aug 18, 2016 at 04:45:30PM +0200, Quentin Glidic wrote: >>> >>> From: Quentin Glidic >>> >>> With this weston_view_destroy() call, Xwayland popups make Weston freeze >>> in a busy-loop (probably

Re: [PATCH weston 2/2] libweston-desktop: fix unsetting fullscreen/maximize with wl_shell

2016-09-06 Thread Giulio Camuffo
2016-09-06 7:04 GMT+03:00 Jonas Ã…dahl : > On Sun, Sep 04, 2016 at 06:50:47PM +0300, Giulio Camuffo wrote: >> --- >> libweston-desktop/wl-shell.c | 11 +++ >> 1 file changed, 11 insertions(+) >> >> diff --git a/libweston-desktop/wl-shell.c b/libweston-desktop/wl-shell.c >> index 74ce473..71

[PATCH wayland] server: allow removing any wl_listener from a signal when emitted

2016-09-06 Thread Giulio Camuffo
wl_list_for_each_safe, which was used by wl_signal_emit is not really safe. If a signal has two listeners, and the first one removes and re-inits the second one, it would enter an infinite loop. This commit adds a wl_list_iterate_safe() function which is used by wl_signal_emit() and adds a test con