[ANNOUNCE] libinput 1.0.2

2015-10-20 Thread Peter Hutterer
libinput 1.0.2 is now available. This release contains two tapping fixes. A multitap (triple tap, quadruple tap, ...) caused one too many click events, particularly noticable during a double-tap-and-hold dragging process. The second fix avoids erroneous click events when two fingers are placed on

Re: [PATCH libinput 2/2] extend tools to print and display touch event properties

2015-10-20 Thread Peter Hutterer
On Sun, Sep 06, 2015 at 02:55:13PM +0200, Andreas Pokorny wrote: > event-gui draws the touch contact as two concentric ellipses that indicate > contact pressure through oppacity. > > Signed-off-by: Andreas Pokorny > --- > tools/event-debug.c | 30 -- > tools/event-gui

Re: Unstable protocol name breakage

2015-10-20 Thread Jonas Ådahl
On Tue, Oct 20, 2015 at 09:51:34AM +0200, Jan Arne Petersen wrote: > Hi, > > On 20/10/15 04:22, Jonas Ådahl wrote: > > input-method.xml: This one I think might actually be fine to just apply the > > naming schema, as the protocol itself has Wayland core principle violations > > that need to be sol

Re: Unstable protocol name breakage

2015-10-20 Thread Jonas Ådahl
On Tue, Oct 20, 2015 at 06:42:24AM +0200, Mariusz Ceier wrote: > On 20 October 2015 at 05:59, Jonas Ådahl wrote: > > > On Tue, Oct 20, 2015 at 05:26:45AM +0200, Mariusz Ceier wrote: > > > Hi, > > > > > > On 20 October 2015 at 04:22, Jonas Ådahl wrote: > > > > > > > Hi again, > > > > > > > > I wa

Re: [PATCH] weston: implement inert objects for keyboard/pointer/touch

2015-10-20 Thread Jonas Ådahl
On Wed, Oct 21, 2015 at 12:23:10AM +0200, Hardening wrote: > Le 20/10/2015 17:12, Bryce Harrington a écrit : > > On Tue, Oct 20, 2015 at 10:39:51AM +0200, Hardening wrote: > >> Le 20/10/2015 10:24, Bryce Harrington a écrit : > >>> On Mon, Oct 19, 2015 at 03:47:19PM +0200, David FORT wrote: > T

Re: [PATCH] weston: implement inert objects for keyboard/pointer/touch

2015-10-20 Thread Hardening
Le 20/10/2015 17:12, Bryce Harrington a écrit : > On Tue, Oct 20, 2015 at 10:39:51AM +0200, Hardening wrote: >> Le 20/10/2015 10:24, Bryce Harrington a écrit : >>> On Mon, Oct 19, 2015 at 03:47:19PM +0200, David FORT wrote: This patch implements inert objects for wl_keyboard, wl_pointer and >

Re: [RFC] weston: implement inert objects for keyboard/pointer/touch

2015-10-20 Thread Derek Foreman
On 19/10/15 08:47 AM, David FORT wrote: > This is the second version. I have restored the ref counting of input devices, > I think with the name weston_seat_init_pointer is not accurate, perhaps > weston_seat_add_pointer_device would be better. I'm really wondering if it's > the weston core that s

Re: [PATCH] dmabuf: get supported dmabuf formats from compositor backend

2015-10-20 Thread Bryce Harrington
On Tue, Oct 20, 2015 at 04:54:30PM +0200, Fabien Dessenne wrote: > Add the possibility for the compositor backend to provide with the list > of supported pixel formats for dmabuf-based buffers. > This information is used by linux_dmabuf to inform clients when binding. > > Signed-off-by: Fabien Des

[PATCH] dmabuf: get supported dmabuf formats from compositor backend

2015-10-20 Thread Fabien Dessenne
Add the possibility for the compositor backend to provide with the list of supported pixel formats for dmabuf-based buffers. This information is used by linux_dmabuf to inform clients when binding. Signed-off-by: Fabien Dessenne --- src/compositor.h | 2 ++ src/linux-dmabuf.c | 16 +++

Re: [PATCH] weston: implement inert objects for keyboard/pointer/touch

2015-10-20 Thread Bryce Harrington
On Tue, Oct 20, 2015 at 10:39:51AM +0200, Hardening wrote: > Le 20/10/2015 10:24, Bryce Harrington a écrit : > > On Mon, Oct 19, 2015 at 03:47:19PM +0200, David FORT wrote: > >> This patch implements inert objects for wl_keyboard, wl_pointer and > >> wl_touch. > >> The target case is when the serv

Re: Unstable protocol name breakage

2015-10-20 Thread Daniel Stone
Hi, On 20 October 2015 at 06:16, Jasper St. Pierre wrote: > On Mon, Oct 19, 2015 at 7:22 PM, Jonas Ådahl wrote: >> xdg-shell.xml: Should we bite the bullet and rename this one, or just >> continue >> letting its stability state be non-discoverable? It's clearly already used, >> and >> renaming

Re: iio sensors, acceleration and gyro.

2015-10-20 Thread Bastien Nocera
On Tue, 2015-10-20 at 08:39 +1000, Peter Hutterer wrote: > On Mon, Oct 19, 2015 at 12:20:27PM -0500, Mike Mestnik wrote: > > Hello, > >   I've been working on a project called iio-sensor-proxy, it's a > > project to take sensor readings and make them available over > > dbus.  I > > feel that this t

Re: [PATCH] weston: implement inert objects for keyboard/pointer/touch

2015-10-20 Thread Hardening
Le 20/10/2015 10:24, Bryce Harrington a écrit : > On Mon, Oct 19, 2015 at 03:47:19PM +0200, David FORT wrote: >> This patch implements inert objects for wl_keyboard, wl_pointer and wl_touch. >> The target case is when the server has just send a capability event about a >> disappearing object, and t

Re: [PATCH v2 0/4] Enum and bitfield XML attributes

2015-10-20 Thread Auke Booij
On 19 October 2015 at 23:21, Auke Booij wrote: > There has been plenty of discussion regarding the introduction of new XML > attributes. This series of patches improves on my earlier attempt to find > common ground in this. > > Major exclusions from these patches are: > > - Support for cross-inter

Re: [PATCH] weston: implement inert objects for keyboard/pointer/touch

2015-10-20 Thread Bryce Harrington
On Mon, Oct 19, 2015 at 03:47:19PM +0200, David FORT wrote: > This patch implements inert objects for wl_keyboard, wl_pointer and wl_touch. > The target case is when the server has just send a capability event about a > disappearing object, and the client binds the corresponding object. We bind an

Re: [PATCH v2 3/4] scanner: enforce correct argument type for enums

2015-10-20 Thread Bryce Harrington
On Mon, Oct 19, 2015 at 11:21:25PM +0100, Auke Booij wrote: > The scanner now checks whether arguments that have an associated > have the right type. > An argument with an enum attribute must be of type int or uint, > and if the with that name has the bitfield attribute > set to true, then the ar

Re: Unstable protocol name breakage

2015-10-20 Thread Jan Arne Petersen
Hi, On 20/10/15 04:22, Jonas Ådahl wrote: > input-method.xml: This one I think might actually be fine to just apply the > naming schema, as the protocol itself has Wayland core principle violations > that need to be solved, i.e. any implementor of this is already broken (by > principle). > > text

Re: [PATCH v2 1/4] doc: document the enum and bitfield attributes

2015-10-20 Thread Bryce Harrington
On Tue, Oct 20, 2015 at 12:01:14AM -0700, Bryce Harrington wrote: > On Mon, Oct 19, 2015 at 11:21:23PM +0100, Auke Booij wrote: > > Introduce the enum and bitfield attributes, which allow you to refer to the > > enum > > you are expecting in an argument, and specify which enums are to be thought

Re: [PATCH v2 2/4] protocol: specify enum and bitfield attributes

2015-10-20 Thread Bryce Harrington
On Mon, Oct 19, 2015 at 11:21:24PM +0100, Auke Booij wrote: > Signed-off-by: Auke Booij Reviewed-by: Bryce Harrington > --- > protocol/wayland.xml | 34 +- > 1 file changed, 17 insertions(+), 17 deletions(-) > > diff --git a/protocol/wayland.xml b/protocol/wayl

Re: [PATCH v2 1/4] doc: document the enum and bitfield attributes

2015-10-20 Thread Bryce Harrington
On Mon, Oct 19, 2015 at 11:21:23PM +0100, Auke Booij wrote: > Introduce the enum and bitfield attributes, which allow you to refer to the > enum > you are expecting in an argument, and specify which enums are to be thought of > as bitfields. > > Signed-off-by: Auke Booij > --- > doc/publican/so