Re: [PATCH weston v2 3/5] compositor: Emit wl_pointer_gesture_* events on libinput gesture events

On Thu, Jul 23, 2015 at 07:00:29PM +0200, Carlos Garnacho wrote: > The translation is fairly straightforward so far, it would be convenient > if gestures went through the pointer grab interface, but this is not done > at the moment. > > Signed-off-by: Carlos Garnacho Reviewed-by: Jonas Ådahl >

Re: [PATCH weston v2 2/5] compositor: Implement wl_pointer_gesture_swipe/pinch interfaces

On Thu, Jul 23, 2015 at 07:00:28PM +0200, Carlos Garnacho wrote: > Each of these come with a getter on wl_pointer, which takes care > of creating the resource. The focused resources list is maintained > in sync with the pointer's. I guess this commit message needs to be updated. > > Signed-off-b

[PATCH weston 1/3] input: Keep per client pointer resources in their own structs

Keep all per client wl_pointer resources in a new struct called 'weston_pointer_client'. When focus changes, instead of moving a list of resources between different lists, just change the focused pointer client. The intention with this is to make it easier to add wl_pointer extensions that share t

[PATCH weston 2/3] input: Provide microsecond timestamps in motion events

Provide timestamps with microsecond granularity if the backend can provide it. Backends that can't should set it to 0. Signed-off-by: Jonas Ådahl --- This requires libinput master branch. I didn't add any dependency checking since libinput hasn't been released with the new _get_time_usec functio

[PATCH weston v3 3/3] Introduce wl_relative_pointer interface

A wl_relative_pointer object is an extension to the wl_pointer interface only used for emitting relative pointer events. It will only emit events when the parent pointer has focus. To get a relative pointer object, use the get_relative_pointer request of the global wl_relative_pointer_manager obje

Re: [PATCH weston v2 1/5] protocol: Add _wl_pointer_gestures (swipe/pinch) protocol

On Wed, Jul 29, 2015 at 10:52:18AM +0800, Jonas Ådahl wrote: > On Thu, Jul 23, 2015 at 07:00:27PM +0200, Carlos Garnacho wrote: > > The whole feature is exposed by the wl_pointer_gestures global > > resource, which can be used to obtain individual swipe/pinch > > gesture interfaces for a given wl_p

Re: [PATCH weston v2 1/5] protocol: Add _wl_pointer_gestures (swipe/pinch) protocol

On Thu, Jul 23, 2015 at 07:00:27PM +0200, Carlos Garnacho wrote: > The whole feature is exposed by the wl_pointer_gestures global > resource, which can be used to obtain individual swipe/pinch > gesture interfaces for a given wl_pointer. > > The lifetime and progress of gestures is maintained by t

Re: [PATCH libinput] test: add a bunch of libinput_dispatch() before timeout calls

On Wed, Jul 29, 2015 at 10:35:36AM +1000, Peter Hutterer wrote: > 98346f6a1aa added a warning about timeouts expiring before now. Those warnings > are triggered by a bunch of tests where we have events, then a timeout, then a > libinput_dispatch(). > > All these are bugs in the test, since we can'

[PATCH libinput] =?UTF-8?q?touchpad:=20update=20the=20thumb=20mov?= =?UTF-8?q?e=20timeout=20to=20=C2=B5s?=

And add a #define for it so we stop hiding it. Signed-off-by: Peter Hutterer --- 300us was enough to pass the test on my laptop, but valgrind on the test VMs failed them... src/evdev-mt-touchpad.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/src/evdev-mt-touchpad.c b/sr

[PATCH libinput] test: add a bunch of libinput_dispatch() before timeout calls

98346f6a1aa added a warning about timeouts expiring before now. Those warnings are triggered by a bunch of tests where we have events, then a timeout, then a libinput_dispatch(). All these are bugs in the test, since we can't guarantee the order of fds (and thus which fd the events are pulled off

[PATCH libinput] touchpad: drop distance threshold to detect pinches

This gives us too many false positives of 2fg scroll being detected as pinch gesture. Reporter in [1] uses index+ring finger and thus exceeds the distance easily (that's admittedly a special case). This is worsed by the lack of a client stack that handles the gestures. User's don't see that they'r

Re: [PATCH wayland 2/2] Introduce WAYLAND_SERVER_SOCKET to change the path where the server will create the socket.

Introduce WAYLAND_SERVER_SOCKET to change the path where the server will create the socket. It will be possible for a nested compositor to offer a socket located on WAYLAND_SERVER_SOCKET path while connecting to the main compositor socket that is located on WAYLAND_DISPLAY path. --- src/waylan

[PATCH wayland 1/2] Extend WAYLAND_DISPLAY and name parameter semantics to support absolute paths.

Extend WAYLAND_DISPLAY and name parameter semantics to support absolute paths. For example WAYLAND_DISPLAY="/my/path/wayland-2" or connect_to_socket("/my/path/wayland-2"). --- doc/man/wl_display_connect.xml | 8 src/wayland-client.c | 22 +- src/wayland-

[PATCH wayland] Introduce WAYLAND_SERVER_SOCKET_DIR to change socket directory without changing XDG_RUNTIME_DIR.

Introduce WAYLAND_SERVER_SOCKET_DIR to change socket directory without changing XDG_RUNTIME_DIR. This might be useful to change socket directory in case wl_display_add_socket_auto is used. For example this will change the socket path for weston without using any command line argument. This envv