[ANNOUNCE] libinput 1.5.1

A larger number of patches than usual for a minor release but most of these have little to no functional impact and are just cleanups. The new bits here are: - We now really ignore joysticks. The code was in before but didn't work correctly - A quirk for the YHP Compat 6910 - a new check to make

Re: [PATCH wayland] protocol: spell out that we're using linux/input-event-codes.h key codes

On Thu, Nov 10, 2016 at 10:22:41AM +, Daniel Stone wrote: > Hi, > > On 10 November 2016 at 05:19, Peter Hutterer wrote: > > A side-note here: my first version sent to Jonas privately had a reserved > > range for any key with the highest bit set. The idea here was to

Re: [PATCH] doc: Fix a typo in the client documentation

Hi Moritz, > On Nov 6, 2016, at 9:35 AM, Moritz Kiefer > wrote: > > Signed-off-by: Moritz Kiefer Reviewed-by: Yong Bakos yong > --- > doc/publican/sources/Client.xml | 2 +- > 1 file changed,

[PATCH weston] text-input: Clear out context->input pointer

If we destroy the text_input (e.g. due to surface deactivation) whilst the IM manager (the client holding the input_method_context resource, usually weston-keyboard) sends an event, we can hit a segfault in text-backend. This is because we free the text_input structure, but don't actually clear

Re: [PATCH wayland] tests: Test wl_message_count_arrays

On Thu, 3 Nov 2016 13:42:54 -0700 Yong Bakos wrote: > From: Yong Bakos > > message-test.c did not cover wl_message_count_arrays, so add one test that > specifically tests this method. Note that this exposes wl_message_count_arrays > in a

Re: Weston

> why is it using weston-launch when you have systemd? I am not sure I understand; that file is a service that's enable via systemctl and it launches weston once the graphic is ready, right? How else would you start weston on boot? Is there already a weston service I am missing? That might

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

On Mon, 31 Oct 2016 06:46:18 -0700 Yong Bakos wrote: > 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

Re: [PATCH wayland v2] scanner: Remove return doxygen annotation

On Wed, 7 Sep 2016 23:44:01 -0700 Bryce Harrington wrote: > On Wed, Sep 07, 2016 at 06:25:27AM -0700, Yong Bakos wrote: > > From: Yong Bakos > > > > Replace \returns with just Returns, as this is not a doxygen comment block. > > (Avoids

Re: [PATCH wayland] tests: Use unique XDG_RUNTIME_DIR

On Thu, 10 Nov 2016 11:14:03 + Daniel Stone wrote: > Rather than using a hardcoded 'wayland-tests' directory under > the existing XDG_RUNTIME_DIR to use as the new runtime dir, use mkdtemp > to guarantee uniqueness. This fixes make -jN check, as well as just >

[PATCH wayland] tests: Use unique XDG_RUNTIME_DIR

Rather than using a hardcoded 'wayland-tests' directory under the existing XDG_RUNTIME_DIR to use as the new runtime dir, use mkdtemp to guarantee uniqueness. This fixes make -jN check, as well as just happening to run 'make check' twice from the same session. Signed-off-by: Daniel Stone

Re: [PATCH wayland 1/2] protocol: Describe wl_registry as singleton

On Thu, 29 Sep 2016 23:59:58 -0700 Yong Bakos wrote: > From: Yong Bakos > > Other singleton objects in the protocol are described as such. > > Add a singleton adjective to the wl_registry description, making it > similar to other descriptions.

Re: [PATCH wayland] shm: Make shm_pool_interface static const

On Tue, 16 Aug 2016 11:12:35 +0300 Pekka Paalanen wrote: > On Fri, 12 Aug 2016 12:41:47 -0700 > Bryce Harrington wrote: > > > On Fri, Aug 12, 2016 at 12:04:41PM -0700, Yong Bakos wrote: > > > From: Yong Bakos > > > > > >

Re: [PATCH wayland] protocol: spell out that we're using linux/input-event-codes.h key codes

Hi, On 10 November 2016 at 05:19, Peter Hutterer wrote: > A side-note here: my first version sent to Jonas privately had a reserved > range for any key with the highest bit set. The idea here was to have a > range defined that we'll never touch during protocol updates

Re: [PATCH weston 2/2] compositor-drm: Restore use-current-mode functionality

On 09.11.2016 15:43, Daniel Stone wrote: > Hi Armin, > Hi, > On 9 October 2016 at 22:48, Armin Krezović wrote: >> diff --git a/compositor/main.c b/compositor/main.c >> index 320305c..ffeadfb 100644 >> --- a/compositor/main.c >> +++ b/compositor/main.c >> @@ -78,6

Re: [PATCH wayland 3/3] tests: add scanner tests

On Thu, 10 Nov 2016 11:11:51 +0100 Emilio Pozuelo Monfort wrote: > On 10/11/16 10:57, Pekka Paalanen wrote: > > From: Pekka Paalanen > > > > Add tests that ensure that wayland-scanner output for a given input does > > not change unexpectedly.

Re: [PATCH wayland 3/3] tests: add scanner tests

On 10/11/16 10:57, Pekka Paalanen wrote: > From: Pekka Paalanen > > Add tests that ensure that wayland-scanner output for a given input does > not change unexpectedly. This makes it very easy to review > wayland-scanner patches. > > Before, when patches were

[PATCH wayland 0/3] Ensure wayland-scanner output does not change

From: Pekka Paalanen This is a patch series that adds a test to ensure that wayland-scanner output does not change unexpectedly. For details, see patch 3/3. Patch 1 adds the data set, patch 2 is preparation, and patch 3 is the meat. Patch 1 is huge. I decided to

[PATCH wayland 2/3] Makefile: do not put TESTS into check_PROGRAMS

From: Pekka Paalanen If you assign TESTS into check_PROGRAMS, you cannot add a test that is not built from source files. Instead, use a temporary variable built_test_programs to hold the names that are both programs built from source files and tests to execute.

[PATCH wayland 1/3] tests: add data files for future wayland-scanner test

From: Pekka Paalanen This patch adds the input and reference output data files for the wayland-scanner tests to be added by the following patch. The data files are split into their own patch because they are extremely uninteresting to review: - example.xml is

[PATCH wayland 3/3] tests: add scanner tests

From: Pekka Paalanen Add tests that ensure that wayland-scanner output for a given input does not change unexpectedly. This makes it very easy to review wayland-scanner patches. Before, when patches were proposed for wayland-scanner, I had to build wayland

Re: Shell surface positioning

On Thu, Nov 10, 2016 at 6:20 AM, Jonas Ådahl wrote: > On Wed, Nov 09, 2016 at 10:30:45AM +0100, Jan Synacek wrote: >> Hello, >> >> I'm playing around with libwayland-client, implementing a simple >> application. I made the middle mouse button move the "window" using >>

Re: Weston

It looks like you want something like benja ( https://benja.io/ ) which is Weston + Electron based. It uses a service: https://github.com/WebReflection/benja/blob/gh-pages/os/sh/weston-compositor.service You can enable it via `systemctl enable weston-compositor` You also need to put ``` [shell]