Re: Release schedule

2018-06-14 Thread Derek Foreman
On 2018-06-14 02:08 AM, Pekka Paalanen wrote: > On Wed, 13 Jun 2018 21:05:03 -0400 > ferreiradaselva wrote: > >> Any chance of the XDG decoration protocol being part of this release plan? > > Hi, > > wayland-protocols is not part of this release plan. It is much more > free to release at

[PATCH wayland] .gitlab-ci.yml: collect the distcheck error logs

2018-06-14 Thread Emil Velikov
From: Emil Velikov Currently we issue both check and distcheck, as reportedly there has been cases in the past one works, while the other doesn't. Yet we only collect the check artefacts (test logs). Correct that, by picking the distcheck ones as well. Note: the build-*/wayland*/ directory is

[PATCH wayland 8/8] fixup! scanner: initialize .{method, event}_count via ARRAY_SIZE

2018-06-14 Thread Emil Velikov
--- tests/data/example-code.c | 73 + tests/data/small-code-core.c| 5 +-- tests/data/small-code.c | 5 +-- tests/data/small-private-code.c | 5 +-- 4 files changed, 46 insertions(+), 42 deletions(-) diff --git

[PATCH wayland 6/8] fixup! scanner: use c99 initializers for the interface symbols

2018-06-14 Thread Emil Velikov
--- tests/data/example-code.c | 124 +++- tests/data/small-code-core.c| 6 +- tests/data/small-code.c | 6 +- tests/data/small-private-code.c | 6 +- 4 files changed, 67 insertions(+), 75 deletions(-) diff --git

[PATCH wayland 7/8] scanner: initialize .{method, event}_count via ARRAY_SIZE

2018-06-14 Thread Emil Velikov
From: Emil Velikov Demystify the final magic value within the generated files. Signed-off-by: Emil Velikov --- src/scanner.c | 9 + 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/src/scanner.c b/src/scanner.c index 22b1daa..8f469e9 100644 --- a/src/scanner.c +++

[PATCH wayland 4/8] fixup! scanner: use c99 initializers for the request/events arrays

2018-06-14 Thread Emil Velikov
--- tests/data/example-code.c | 238 tests/data/small-code-core.c| 8 +- tests/data/small-code.c | 8 +- tests/data/small-private-code.c | 8 +- 4 files changed, 131 insertions(+), 131 deletions(-) diff --git

[PATCH wayland 5/8] scanner: use c99 initializers for the interface symbols

2018-06-14 Thread Emil Velikov
From: Emil Velikov Provides some clarity and removes the unnecessary zero/NULL initialization. Signed-off-by: Emil Velikov --- src/scanner.c | 10 +++--- 1 file changed, 3 insertions(+), 7 deletions(-) diff --git a/src/scanner.c b/src/scanner.c index fb3c808..22b1daa 100644 ---

[PATCHv2 wayland 0/8] wayland-scanner: produce code with c99 initializers

2018-06-14 Thread Emil Velikov
Hi all, Here's a take v2 of the series, with the following changes: - don't trim trailing NULL entries from the wl_interfaces* array - updated tests - separate patches to ease review, to be squashed On the question of why, despite the aesthetics these patches make the generated files actually

[PATCH wayland 3/8] scanner: use c99 initializers for the request/events arrays

2018-06-14 Thread Emil Velikov
From: Emil Velikov Makes things a bit less magical, should you be looking in the file. Signed-off-by: Emil Velikov --- src/scanner.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/scanner.c b/src/scanner.c index 4b49593..fb3c808 100644 --- a/src/scanner.c +++

[PATCH wayland 2/8] fixup! scanner: use c99 initializers for the wl_interface * array

2018-06-14 Thread Emil Velikov
--- tests/data/example-code.c | 190 tests/data/small-code-core.c| 16 ++-- tests/data/small-code.c | 16 ++-- tests/data/small-private-code.c | 16 ++-- 4 files changed, 119 insertions(+), 119 deletions(-) diff --git

[PATCH wayland 1/8] scanner: use c99 initializers for the wl_interface * array

2018-06-14 Thread Emil Velikov
From: Emil Velikov Makes it a bit more obvious, should you be reading through the generated code. We might even drop the NULL entries (at a later stage) making things shorter and easier to read. v2: don't alter the array size by discarding trailing NULL entries Signed-off-by: Emil Velikov

RE: Issue with initial window position

2018-06-14 Thread PrasanthKumar P . A .
Hi, Thank you all.Will try this and get back to you asap. Thanks, Prasanth From: Ucan, Emre (ADITG/ESB) [eu...@de.adit-jv.com] Sent: 14 June 2018 17:52 To: PrasanthKumar P.A. Cc: wayland-devel@lists.freedesktop.org; Pekka Paalanen Subject: RE: Issue with

Re: Issue with initial window position

2018-06-14 Thread Pekka Paalanen
On Thu, 14 Jun 2018 12:09:03 + PrasanthKumar P.A. wrote: > Hi, > Thank you for your quick response. > These are our concerns. > Our application is a HMI that is to be deployed on IMX8 board. > By design we need to place some QT Qml windows on specified x y > coordinates on the screen .How

RE: Issue with initial window position

2018-06-14 Thread Ucan, Emre (ADITG/ESB)
Hi, You can use IVI Shell with wayland-ivi-extension to realize your use-case. Please check this: https://at.projects.genivi.org/wiki/display/PROJ/Wayland+IVI+Extension+Design Best regards Emre Ucan Engineering Software Base (ADITG/ESB) Tel. +49 5121 49 6937 > -Original Message- >

RE: Issue with initial window position

2018-06-14 Thread PrasanthKumar P . A .
Hi, Thank you for your quick response. These are our concerns. Our application is a HMI that is to be deployed on IMX8 board. By design we need to place some QT Qml windows on specified x y coordinates on the screen .How can we achieve this ? Also I am interested on (If your target

Re: [PATCH wayland 1/3] doc: move Contributing

2018-06-14 Thread Pekka Paalanen
On Thu, 14 Jun 2018 10:58:00 +0100 Daniel Stone wrote: > Hi Pekka, > > On Wed, 13 Jun 2018 at 14:33, Pekka Paalanen wrote: > > Gitlab expects a CONTRIBUTING.md in the root directory, so move our > > guide there. > > > > Conversion to proper markup is a follow-up patch. > > Thanks for these;

Re: Issue with initial window position

2018-06-14 Thread Pekka Paalanen
On Thu, 14 Jun 2018 10:39:57 + PrasanthKumar P.A. wrote: > Dear All, > > I have a Qt Qml application which contains several windows (Qml > windows). I have set the initial positions x,y for these windows but > none of these windows are coming in the corresponding coordinates . Hi, this

Re: Wayland content-protection extension

2018-06-14 Thread Arnaud Vrac
On Wed, Jun 13, 2018 at 12:34 PM, Nautiyal, Ankit K wrote: > Hi All, > > I am working on wayland content-protection protocol extension, to enable > content-protection (HDCP1.4, HDCP2.2) in wayland. > DRM layer already has support for HDCP1.4 and patches for HDCP2.2 are in > review :

Issue with initial window position

2018-06-14 Thread PrasanthKumar P . A .
Dear All, I have a Qt Qml application which contains several windows (Qml windows). I have set the initial positions x,y for these windows but none of these windows are coming in the corresponding coordinates .Each time when I restart the application the windows are coming in the random

Re: how to handle the last_error of wl_display

2018-06-14 Thread Pekka Paalanen
On Thu, 14 Jun 2018 16:59:35 +0800 zou lan wrote: > Dear pekka & All: > > I find a wayland application report error about allocate memory fail. > I check the code, after request to weston to allocate dma buffer, it call > wl_display_roundtrip(). > But this function return very fast, it doesn't

Re: is there anyway to get which compositor did the client "wl_display" object connected?

2018-06-14 Thread Pekka Paalanen
On Thu, 14 Jun 2018 16:59:54 +0800 (CST) tugouxp <13824125...@163.com> wrote: > hi: > > thanks for you answer. > > i need this on webkitgtk debug scenario, webkitgtk has a nested > compositor, it seems the "webprocess" of webkit need both connect the > nest compositer and the system

Re: [PATCH wayland 1/3] doc: move Contributing

2018-06-14 Thread Daniel Stone
Hi Pekka, On Wed, 13 Jun 2018 at 14:33, Pekka Paalanen wrote: > Gitlab expects a CONTRIBUTING.md in the root directory, so move our > guide there. > > Conversion to proper markup is a follow-up patch. Thanks for these; both series are: Reviewed-by: Daniel Stone Cheers, Daniel

Re: [PATCH wayland-web 2/2] index: add link to Gitlab repositories

2018-06-14 Thread Pekka Paalanen
On Thu, 14 Jun 2018 08:53:51 +1000 Peter Hutterer wrote: > On Wed, Jun 13, 2018 at 04:32:26PM +0300, Pekka Paalanen wrote: > > From: Pekka Paalanen > > > > We migrated some. > > > > Signed-off-by: Pekka Paalanen > > --- > > index.html | 3 ++- > > 1 file changed, 2 insertions(+), 1

Re:Re: is there anyway to get which compositor did the client "wl_display" object connected?

2018-06-14 Thread tugouxp
hi: thanks for you answer. i need this on webkitgtk debug scenario, webkitgtk has a nested compositor, it seems the "webprocess" of webkit need both connect the nest compositer and the system compositors, so there are two some of objecet sets with same client type. for example: i

how to handle the last_error of wl_display

2018-06-14 Thread zou lan
Dear pekka & All: I find a wayland application report error about allocate memory fail. I check the code, after request to weston to allocate dma buffer, it call wl_display_roundtrip(). But this function return very fast, it doesn't block until the create events back. I suspect the

Re: [RFC PATCH wayland 3/3] contributing: reformat code examples

2018-06-14 Thread Pekka Paalanen
On Thu, 14 Jun 2018 08:53:19 +1000 Peter Hutterer wrote: > On Wed, Jun 13, 2018 at 04:32:24PM +0300, Pekka Paalanen wrote: > > From: Pekka Paalanen > > > > Before, the code examples looked good in the file, but a hard tab was > > rendered as 4 spaces by Gitlab. > > > > Now, Gitlab renders the

Re: [PATCH wayland 1/3] doc: move Contributing

2018-06-14 Thread Pekka Paalanen
On Thu, 14 Jun 2018 08:48:10 +1000 Peter Hutterer wrote: > On Wed, Jun 13, 2018 at 04:32:22PM +0300, Pekka Paalanen wrote: > > From: Pekka Paalanen > > > > Gitlab expects a CONTRIBUTING.md in the root directory, so move our > > guide there. > > > > Conversion to proper markup is a follow-up

Re: is there anyway to get which compositor did the client "wl_display" object connected?

2018-06-14 Thread Pekka Paalanen
On Thu, 14 Jun 2018 10:30:35 +0800 (CST) tugouxp <13824125...@163.com> wrote: > hi folks: >there are scenario that when more than one compositor (such as nested > compositor" ) exists. > > > how to distinguish which server do the client "wl_display*" object connected? > is there any way

Re: Release schedule

2018-06-14 Thread Pekka Paalanen
On Wed, 13 Jun 2018 21:05:03 -0400 ferreiradaselva wrote: > Any chance of the XDG decoration protocol being part of this release plan? Hi, wayland-protocols is not part of this release plan. It is much more free to release at arbitrary times and usually does not go through a freeze period