Re: [PATCH v7 wayland-protocols] Add the tablet protocol

On Thu, Mar 31, 2016 at 02:17:02PM +0200, Carlos Garnacho wrote: > Hey :), > > On Thu, Mar 31, 2016 at 9:32 AM, Peter Hutterer > wrote: > > sorry about the delay, this one slipped through > > > > On Fri, Mar 11, 2016 at 04:12:55PM -0800, Jason Gerecke wrote: > >> On

Re: Collaboration on standard Wayland protocol extensions

On Thu, Mar 31, 2016 at 05:37:10PM +0200, Benoit Gschwind wrote: > Hello Drew, > > After reading the thread stream, I think there is two mixed questions in > your email that is missleading. And most reply try to address both in > one reply. I thing Daniel get the point (if I understood him well).

Re: history/semantics of uint32_t name

On Thu, Mar 31, 2016 at 06:48:06PM -0500, Yong Bakos wrote: > Hi, > I've been investigating the semantics of the name parameter within the > wl_registry interface, prompted by a recent dialog regarding my patch of arg > summary attributes in wayland.xml. > > I've dug around the Weston source to

Re: [PATCH wayland] scanner: Fix spacing of @param

On Thu, Mar 31, 2016 at 06:55:54PM -0500, Yong Bakos wrote: > From: Yong Bakos > > Adds one space to the @param lines in generated .h files, > aligning the indentation with the rest of the comment block. > > Signed-off-by: Yong Bakos

[PATCH libinput 3/4] test: add a test for the T450 dropped motion events

Signed-off-by: Peter Hutterer --- test/touchpad.c | 67 + 1 file changed, 67 insertions(+) diff --git a/test/touchpad.c b/test/touchpad.c index be9c566..4651b7a 100644 --- a/test/touchpad.c +++ b/test/touchpad.c

[PATCH libinput 4/4] touchpad: reset the motion history on significant negative pressure changes

Resetting the motion history has the side-effect of swallowing movements, we don't calculate deltas until we have 4 motion events. During a finger release, we're likely to get a large pressure change between two events, resetting the motion history prevents the cursor from jumping on release. The

[PATCH libinput 1/4] test: apply the new t450 model flag to our X1 3rd test device

Signed-off-by: Peter Hutterer --- test/litest-device-synaptics-x1-carbon-3rd.c | 11 +++ 1 file changed, 11 insertions(+) diff --git a/test/litest-device-synaptics-x1-carbon-3rd.c b/test/litest-device-synaptics-x1-carbon-3rd.c index 718d108..23d9c5b 100644 ---

[PATCH libinput 2/4] touchpad: only post motion events if we have motion

Because our delta calculation factors in previous events on touchpads (to reduce jitter) we may get a nonzero delta if we have an event that doesn't actually change x or y. Drop the t->dirty workaround introduced in a608d9d, an event that virtually disappears can mess up our state machines.

[PATCH wayland] scanner: Fix spacing of @param

From: Yong Bakos Adds one space to the @param lines in generated .h files, aligning the indentation with the rest of the comment block. Signed-off-by: Yong Bakos --- src/scanner.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff

Re: history/semantics of uint32_t name

wl_registry and wl_registry.bind are about globals and creating new instances of globals. A compositor can opt to provide a new global interface by using the wl_global_create API. Immediately, an event is broadcasted to all clients: the wl_registry.global event, which contains a name (the

history/semantics of uint32_t name

Hi, I've been investigating the semantics of the name parameter within the wl_registry interface, prompted by a recent dialog regarding my patch of arg summary attributes in wayland.xml. I've dug around the Weston source to see what values are passed as the name argument, and where it goes...

Collaboration on standard Wayland protocol extensions

hello, i have a proposal for this first time using a mailing list so i hope i do it right-ish protocol for screenshots: client -> server: "can i get a screenshot ?" server -> client: "sure, here it is" / "no" server would send the screenshot via memfd or write() or something. something like

Re: Collaboration on standard Wayland protocol extensions

Hello Drew, After reading the thread stream, I think there is two mixed questions in your email that is missleading. And most reply try to address both in one reply. I thing Daniel get the point (if I understood him well). I read the two following questions: [1] As almost all compositor will

Re: [PATCH] protocol: Add summaries to event parameters

> On Mar 30, 2016, at 12:53 PM, Bryce Harrington wrote: > > On Tue, Mar 29, 2016 at 06:04:49PM -0500, Yong Bakos wrote: >> From: Yong Bakos >> >> All event arg elements now have an appropriate summary attribute. >> This was conducted mostly in

Re: [PATCH v7 wayland-protocols] Add the tablet protocol

Hey :), On Thu, Mar 31, 2016 at 9:32 AM, Peter Hutterer wrote: > sorry about the delay, this one slipped through > > On Fri, Mar 11, 2016 at 04:12:55PM -0800, Jason Gerecke wrote: >> On 03/08/2016 10:10 PM, Peter Hutterer wrote: >> > Signed-off-by: Peter Hutterer

Re: [Spice-devel] Questions about experimental Spice compositor rebase

Hey, On Sun, Feb 28, 2016 at 03:36:58PM +0100, Fabio Fantoni wrote: > > I did fast build tests, I fixed one my mistake in Makefile.am and after I > had this error: > >src/spice/weston_basic_event_loop.h:27:31: fatal error: weston/compositor.h: > >No such file or directory > I fixed with this

Re: Collaboration on standard Wayland protocol extensions

Hi; On 28 March 2016 at 15:55, Drew DeVault wrote: > You're still not grasping the scope of this. I want you to run this > command right now: > > man ffmpeg-all > > Just read it for a while. You're delusional if you think you can > feasibly implement all of these features in the

Re: Collaboration on standard Wayland protocol extensions

On 29/03/16 13:11, Drew DeVault wrote: > I see what you're getting at now. We can get the pid of a wayland > client, though, and from that we can look at /proc/cmdline, from which > we can get the binary path. This line of thinking is a trap: rummaging in /proc/$pid is not suitable for use as a

[PATCH v2 wayland-web] Updated build instructions for wayland-protocols and libwacom

From: Bill Spitzak The Mint instructions have been tested, I had to guess at the Ubuntu12 instructions as I no longer have that machine. v2: Use MAKEFLAGS instead of switches Use instead of & Some rewording of Ubuntu instructions to point out they are old

Re: [PATCH wayland-protocols v5] text: Create second version of text input protocol

On Fri, Mar 25, 2016 at 12:16 AM, Daiki Ueno wrote: > > > + > > + Allows to atomically send state updates from client. > > + > > + This request should follow after a batch of state updating requests > > + like set_surrounding_text, set_content_type,

Re: [PATCH 3/7] gl-renderer: Implement & use check_extension

On Mon, Mar 21, 2016 at 9:37 AM, Miguel A. Vico wrote: > Using strstr(3) for checking for extensions is an error-prone mechanism > as extension names can be prefixes of other extension names (see > https://www.opengl.org/registry/doc/rules.html#using). > > This change

Re: [PATCH wayland-web] Updated build instructions for wayland-protocols and libwacom

On Tue, Mar 8, 2016 at 11:49 PM, Bryce Harrington wrote: > On Wed, Mar 09, 2016 at 12:54:11PM +1000, Peter Hutterer wrote: > > On Tue, Mar 08, 2016 at 06:39:43PM -0800, Bill Spitzak wrote: > > > On Tue, Mar 8, 2016 at 6:12 PM, Peter Hutterer < > peter.hutte...@who-t.net> >

Re: [PATCH 1/2] clients & tests: Unify multiple definitions of x*alloc and related functions

On Tue, Mar 15, 2016 at 3:23 PM, Bryce Harrington wrote: > > --- a/clients/ivi-shell-user-interface.c > +++ b/clients/ivi-shell-user-interface.c > @@ -40,6 +40,7 @@ > #include "shared/config-parser.h" > #include "shared/helpers.h" > #include "shared/os-compatibility.h"

Re: [PATCH wayland-web] Updated build instructions for wayland-protocols and libwacom

> > >> > > > > +# newer version of libwacom is needed than >> in apt >> > > > > +apt install libgudev-1.0-dev >> > > > > +git clone git://git.code.sf.net/p/linuxwacom/libwacom >> > > > > +cd libwacom >> > > > > +make -j 9 && make install >> > > > > +cd .. >> > Is the git repository for libwacom

[PATCH v2 wayland-web] Updated build instructions for wayland-protocols and libwacom

From: Bill Spitzak The Mint instructions have been tested, I had to guess at the Ubuntu12 instructions as I no longer have that machine. v2: Use MAKEFLAGS instead of switches Use instead of & Some rewording of Ubuntu instructions to point out they are old

[PATCH weston 16/16] ivi-shell: remove content_observer leftover

content_observer_notification is removed by the commit: 193e301c740b582f20307e3e08f8373d26ea968f. Therefore, this callback function is unused. Signed-off-by: Emre Ucan --- ivi-shell/ivi-layout-export.h |5 - 1 file changed, 5 deletions(-) diff --git

[PATCH weston 14/16] ivi-shell: rework configure_surface notification

The add_notification_configure_surface API accepts a simple wl_listener instead of a ivi-shell specific notification function. Therefore, the API is renamed to add_listener_configure_surface. This change has several advantages: 1. Code cleanup 2. No dynamic memory allocation. Listeners are

[PATCH weston 15/16] ivi-shell: remove remove_notification_configure_surface

ivi_layout_remove_notification_configure_surface API is removed, because it is not needed after the changes to the ivi_layout_add_notification_configure_surface. Signed-off-by: Emre Ucan --- ivi-shell/ivi-layout-export.h |8 --- ivi-shell/ivi-layout.c| 49

[PATCH weston 13/16] ivi-shell: remove remove_notification_remove_surface

ivi_layout_remove_notification_remove_surface API is removed, because it is not needed after the changes to the ivi_layout_add_notification_remove_surface. Signed-off-by: Emre Ucan --- ivi-shell/ivi-layout-export.h |8 ivi-shell/ivi-layout.c|9

[PATCH weston 09/16] ivi-shell: remove remove_notification_create_layer

ivi_layout_remove_notification_create_layer API is removed, because it is not needed after the changes to the ivi_layout_add_notification_create_layer. Signed-off-by: Emre Ucan --- ivi-shell/ivi-layout-export.h |8 ivi-shell/ivi-layout.c|9

[PATCH weston 12/16] ivi-shell: rework remove_surface notification

The add_notification_remove_surface API accepts a simple wl_listener instead of a ivi-shell specific notification function. Therefore, the API is renamed to add_listener_remove_surface. This change has several advantages: 1. Code cleanup 2. No dynamic memory allocation. Listeners are allocated

[PATCH weston 11/16] ivi-shell: remove remove_notification_remove_layer

ivi_layout_remove_notification_remove_layer API is removed, because it is not needed after the changes to the ivi_layout_add_notification_remove_layer. Signed-off-by: Emre Ucan --- ivi-shell/ivi-layout-export.h |8 ivi-shell/ivi-layout.c|9

[PATCH weston 10/16] ivi-shell: rework remove_layer notification

The add_notification_remove_layer API accepts a simple wl_listener instead of a ivi-shell specific notification function. Therefore, the API is renamed to add_listener_remove_layer. This change has several advantages: 1. Code cleanup 2. No dynamic memory allocation. Listeners are allocated by

[PATCH weston 08/16] ivi-shell: rework create_layer_notification

The add_notification_create_layer API accepts a simple wl_listener instead of a ivi-shell specific notification function. Therefore, the API is renamed to add_listener_create_layer. This change has several advantages: 1. Code cleanup 2. No dynamic memory allocation. Listeners are allocated by

[PATCH weston 06/16] ivi-shell: rework create_surface notification

The add_notification_create_surface API accepts a simple wl_listener instead of a ivi-shell specific notification function. Therefore, the API is renamed to add_listener_create_surface. This change has several advantages: 1. Code cleanup 2. No dynamic memory allocation. Listeners are allocated

[PATCH weston 05/16] ivi-shell: remove layer_remove_notification APIs

ivi_layout_layer_remove_notification and ivi_layout_layer_remove_notification_by_callback APIs are removed, because they are not needed after the changes to the ivi_layout_layer_add_notification. Signed-off-by: Emre Ucan --- ivi-shell/ivi-layout-export.h | 18

[PATCH weston 07/16] ivi-shell: remove remove_notification_create_surface

ivi_layout_remove_notification_remove_surface API is removed, because it is not needed after the changes to the ivi_layout_add_notification_create_surface. Signed-off-by: Emre Ucan --- ivi-shell/ivi-layout-export.h |8 ivi-shell/ivi-layout.c|9

[PATCH weston 04/16] ivi-shell: rework layer_add_notification API

The layer_add_notification API accepts a simple wl_listener instead of a ivi-shell specific notification function. Therefore, the API is renamed to layer_add_listener. This change has several advantages: 1. Code cleanup 2. No dynamic memory allocation. Listeners are allocated by controller

[PATCH weston 00/16] IVI Layout Notification APIs Rework

I changed the interface of the notification APIs to get a wl_listener instead of a ivi-shell specific notification callback function. This change has several advantages: 1. Code cleanup 2. No dynamic memory allocation. Listeners are allocated by controller plugins 3. Remove API is not needed.

[PATCH weston 03/16] ivi-shell: remove surface_remove_notification APIs

ivi_layout_surface_remove_notification and ivi_layout_surface_remove_notification_by_callback APIs are removed, because they are not needed after the changes to the ivi_layout_surface_add_notification. Signed-off-by: Emre Ucan --- ivi-shell/ivi-layout-export.h | 18

[PATCH weston 02/16] ivi-shell: rework surface_add_notification API

The surface_add_notification API accepts a simple wl_listener instead of a ivi-shell specific notification function. Therefore, the API is renamed to surface_add_listener. This change has several advantages: 1. Code cleanup 2. No dynamic memory allocation. Listeners are allocated by controller

[PATCH weston 01/16] ivi-shell: move event_mask to properties struct

I moved the event_mask to ivi_layout_*_properties struct, so that it is easily accessible with get_properties_of_* APIs. Signed-off-by: Emre Ucan --- ivi-shell/ivi-layout-export.h |2 ++ ivi-shell/ivi-layout-private.h |2 -- ivi-shell/ivi-layout.c | 66

Re: Collaboration on standard Wayland protocol extensions

Hi, On 31 March 2016 at 00:16, Drew DeVault wrote: > Simply because xrandr was/is a poorly implemented mess doesn't mean that > we are going to end up making a poorly implemented mess. We have the > benefit of hindsight. After all, xorg is a poorly implemented mess but > we still

Re: Semantics of wl_subcompositor::get_subsurface

On Thu, 24 Mar 2016 08:53:11 +0100 Martin Graesslin wrote: > On Monday, March 21, 2016 11:07:39 AM CET you wrote: > > On Mon, 21 Mar 2016 08:36:59 +0100 > > > > Martin Graesslin wrote: > > > Hi Wayland-devs, > > > > > > while implementing sub-surface

Re: [PATCH libinput] touchpad: fix left-handed top software trackpoint buttons

Hi, On 31-03-16 03:52, Peter Hutterer wrote: The previous code would swap the top software buttons depending on the touchpad's left-handed setting, not the trackpoint setting. Changing both devices to left-handed resulted in a double-swap, i.e. the trackpoint was always right-handed.

Re: [PATCH v7 wayland-protocols] Add the tablet protocol

sorry about the delay, this one slipped through On Fri, Mar 11, 2016 at 04:12:55PM -0800, Jason Gerecke wrote: > On 03/08/2016 10:10 PM, Peter Hutterer wrote: > > Signed-off-by: Peter Hutterer > > Reviewed-by: Daniel Stone > > Reviewed-by: Jonas

Re: wayland crash debugging help required

Hi Pekka Paalanen, Thanks a lot for your comment. As you mentioned this could be the case of multiple threads receiving and dispatching events as I am using [1] qtwayland 5.5.1 and [2] imxeglviv video sink. Both the component uses the wl_display_prepare_read() and wl_display_read_events().