Re: libinput: Disable tap-and-drag

Peter Hutterer wrote: thanks for doing this work. tbh, I'm not a big fan of having this as a configuration option. IMO if you are using tapping as an interaction method on the touchpad, having tap-and-drag available is the natural extension and I don't see why we should disable it. I have the s

[PATCH weston 1/2] simple-touch: Use damage_buffer if available

Signed-off-by: Derek Foreman --- clients/simple-touch.c | 18 +++--- 1 file changed, 15 insertions(+), 3 deletions(-) diff --git a/clients/simple-touch.c b/clients/simple-touch.c index 446f2ca..383d802 100644 --- a/clients/simple-touch.c +++ b/clients/simple-touch.c @@ -56,6 +56,7 @@

[PATCH weston 2/2] compositor-wayland: Use damage_buffer if available

Try to replace most usage of wl_surface.damage with wl_surface.damage_buffer. Some calls are beyond our control, such as the gl_renderer's damage handling. Signed-off-by: Derek Foreman --- src/compositor-wayland.c | 52 ++-- 1 file changed, 42 inserti

Re: [RFC wayland-protocols V3] Add Primary Selection Protocol Version 1

On Wed, Jan 6, 2016 at 7:42 PM, Jonas Ådahl wrote: > > Does this mean that the offer always comes on keyboard focus? Or pointer > focus? Or touch focus? Or does it come a user interaction of some kind? > I think the last one is the intention here. The offer will come just before an event that th