Re: [PATCH wayland] protocol: Bump seat to version 7 and require keymaps be private

Actually... (below) 2018-11-01 (木) の 11:15 -0500 に Derek Foreman さんは書きました: > Weston commit 76829fc4eaea329d2a525c3978271e13bd76c078 (and similar > commits for other compositors) protects the compositor's keyboard > mapping from client damage by duplicating the keymap for every > client. > > On

Re: [PATCH wayland] protocol: Bump seat to version 7 and require keymaps be private

I second: \o/ Don't know if it means much at this point, but as original reporter of the issue I claim this is Reviewed-by: Philipp Kerling ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman

Re: [PATCH] protocol: warn clients about some wl_output properties

Hi, one small comment below. 2018-07-03 (火) の 09:01 -0400 に Simon Ser さんは書きました: > All wl_output properties don't always make sense for all > compositors. > > Some compositors might not implement a "global compositor space", > (e.g. 3D compositors) in which case properties like x and y don't >

Re: [PATCHv3] Add name event to xdg-output

Hi, maybe I missed it at some point in the discussion (sorry if that is the case), but what is your use case for the "name?" What are clients expected to use it for? The description mentions "similar behaviors", but it is unclear to me what you are referring to. Regards, Philipp 2018-04-10 (火)

Re: [PATCHv2] Add name event to xdg-output

Hey, I'll just reiterate one point from the prior discussion. > On Mon, 9 Apr 2018 08:13:15 -0400 > Drew DeVault wrote: > > > Good feedback. > > > > On 2018-04-09 11:09 AM, Pekka Paalanen wrote: > > > Does this name correspond to the physical connector or to the > > > specific

Re: [PATCH weston 00/25] A new touchscreen calibrator

> Do you happen to know of a good readymade program that fakes the > presence of a touch input device with uinput? I'd love to test this > series, but current Weston is far ahead of what my embedded devices > will do; so I'm in the position of mostly relying on the desktop for > testing. I'm not

[RFC weston v2] libweston: Commit subsurfaces before committing root surface

Committing the root surface triggers a commit of the xdg_surface state, which might require the subsurface state already being applied (e.g. when an xdg_toplevel needs to follow size constraints, the subsurfaces must be in the right position and size at the time this is verified). ---

Re: [RFC weston] libweston: Do not include subsurfaces with NULL buffer in bounding box

Hi, thanks for resurrecting this :-) reply below 2017-12-04 (月) の 21:37 + に Daniel Stone さんは書きました: > Hi Philipp, > > On 28 July 2017 at 15:41, Philipp Kerling <pkerl...@casix.org> wrote: > > I was pondering how to remove the window decorations of my > >

[PATCH weston] gl-renderer: Fix crash in dmabuf format query for fallback formats

Since formats is an out parameter, we need to copy to the alloc'ed memory and not over the pointer address. Signed-off-by: Philipp Kerling <pkerl...@casix.org> --- libweston/gl-renderer.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/libweston/gl-renderer.c b/libwes

[PATCH wayland] doc: Document behavior of non-nullable object arguments in clients

--- src/wayland-util.h | 15 +-- 1 file changed, 13 insertions(+), 2 deletions(-) diff --git a/src/wayland-util.h b/src/wayland-util.h index caeac82..b6cbe0e 100644 --- a/src/wayland-util.h +++ b/src/wayland-util.h @@ -78,12 +78,23 @@ extern "C" { * wl_message is to a protocol

[PATCH wayland 2/2] server: Send differentiated errors on wl_registry.bind

This now uses the new error codes introduced to wl_registry instead of abusing WL_DISPLAY_ERROR_INVALID_OBJECT. --- src/wayland-server.c | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/src/wayland-server.c b/src/wayland-server.c index 7225b4e..e33af62 100644 ---

[PATCH wayland 1/2] protocol: Add error enum to wl_registry

As an oversight, wl_registry did not define any errors. At least error 0 is already being sent by libwayland-server although it is - strictly speaking - undefined. Define error 0 to be an invalid global which is also a sort of catch-all error code. Errors 1 (invalid version) and 2 (incompatible

Re: Wayland talk at FOSDEM

Hi Pekka, 2017-12-07 (木) の 09:56 +0200 に Pekka Paalanen さんは書きました: > On Tue, 05 Dec 2017 16:46:41 +0200 > Philipp Kerling <pkerl...@casix.org> wrote: > > > Hey everyone, > > > > I've been thinking about submitting a Wayland-themed talk to the > > FOS

Re: Wayland talk at FOSDEM

Hi, 2017-12-06 (水) の 08:56 +0100 に Silvan Jegen さんは書きました: > Hi > > On Tue, Dec 5, 2017 at 3:46 PM, Philipp Kerling <pkerl...@casix.org> > wrote: > > I've been thinking about submitting a Wayland-themed talk to the > > FOSDEM > > graphics devroom [1] an

Re: Wayland talk at FOSDEM

d. Also I would like > to give short overview about the recent activities in ivi-shell and > usage of waltham. Nice, I'll be looking forward to that. I always wanted to know more about how Wayland is actually being used for IVI. > 2017-12-05 15:46 GMT+01:00 Philipp Kerling <pkerl...@casix.

Wayland talk at FOSDEM

Hey everyone, I've been thinking about submitting a Wayland-themed talk to the FOSDEM graphics devroom [1] and wanted to check with the community if anyone else has considered this or another Wayland topic and whether you think it would be a good idea™. What I would want to talk about is a

Re: Who generate the headers?

Hi, 2017-12-02 (土) の 06:05 -0500 に ferreiradaselva さんは書きました: > Hello, everyone > > I'm still learning how the distribution to the access of the API > works. I'm making a library like GLFW/SDL2 with Wayland as one of the > backends. > > I have in my system `/usr/include` the headers of my

Re: [PATCH wayland-protocols v3 01/17] Add xdg-shell to stable/

Hi, 2017-11-15 (水) の 19:19 +0800 に Jonas Ådahl さんは書きました: > Add a copy of xdg-shell unstable v6 to stable/xdg-shell/xdg- > shell.xml. > Folliwing this commit, it will go through a set of changes, before > being declared stable. I have a question here (before declaring it stable) that I hope was

Re: [wayland + ILM] proxy wrappers usage of wayland 1.11.0 to 1.9.0

Hi, 2017-08-21 (月) の 11:05 +0530 に Vikas Patil さんは書きました: > Thanks a lot Philipp for your comments, it really helped. Now I get > the display correctly. However now I get the segmentation at > different > location with my uses case [1] after back porting patches from > wayland > 1.11.0 to 1.9.0

Re: [wayland + ILM] proxy wrappers usage of wayland 1.11.0 to 1.9.0

Hi, Am Freitag, den 18.08.2017, 18:35 +0530 schrieb Vikas Patil: > Dear All, > > > I have backported following patches from wayland 1.11.0 to 1.9.0 to > test one crash issue [1] . I am able to backport and start Weston > with > it. Is this valid thing to do? > > >

Re: Add serial to wl_output::geometry?

Hi, Am Freitag, den 18.08.2017, 10:47 +0300 schrieb Pekka Paalanen: > On Thu, 03 Aug 2017 08:27:06 -0400 > Simon Ser wrote: > > > Hello, > > I'm writing a Wayland client that needs to keep track of screens > > across reboots. I registered a wl_output::geometry event

[RFC weston] libweston: Do not include subsurfaces with NULL buffer in bounding box

I was pondering how to remove the window decorations of my application (which live in subsurfaces) when going full screen without flickering. At first I just destroyed the surfaces, but that lead to flicker (window without decoration will appear for one frame before the full screen application is

[PATCH weston] desktop-shell: Set surface resizing state during interactive resize

xdg_shell requires this information to be shared with the client in order to conform with the specification. The code to forward this to the client by way of a configure() event is already in place and works fine, it was just never being used until now. Signed-off-by: Philipp Kerling <pk

[PATCH] libweston-desktop/xdg-shell: Check window geometry instead of surface size against configured size

size. Fix by calling weston_desktop_surface_get_geometry and using that size instead of main surface size. Signed-off-by: Philipp Kerling <pkerl...@casix.org> --- libweston-desktop/xdg-shell-v5.c | 7 +-- libweston-desktop/xdg-shell-v6.c | 7 +-- 2 files changed, 10 insertions

[PATCH] desktop-shell: Track focused shell surface by main surface

The focused surface is used for determining whether shell surfaces are activated. They should also be considered activated when a subsurface has focus. Inserting a call to weston_surface_get_main_surface fixes this. seat->focused_surface is only used for shell_surface keyboard focus tracking. ---

Re: [PATCH wayland-protocols v2 02/13] xdg-shell: Rename interfaces

Am Freitag, den 30.06.2017, 15:42 +0800 schrieb Jonas Ådahl: > On Fri, Jun 30, 2017 at 08:48:58AM +0200, Philipp Kerling wrote: > > Hi, > > > > Am Freitag, den 30.06.2017, 13:50 +0800 schrieb Jonas Ådahl: > > > Rename the interfaces according to the wayland

Re: [PATCH wayland-protocols v2 02/13] xdg-shell: Rename interfaces

Hi, Am Freitag, den 30.06.2017, 13:50 +0800 schrieb Jonas Ådahl: > Rename the interfaces according to the wayland-protocols policy. > Since > the name 'xdg_shell' as an interface was already taken (by > xdg-shell-unstable-v5) zxdg_shell_v6 was renamed xdg_wm_base. The > surface role related

[PATCH] extras: Update status for Kodi

Wayland integration in Kodi was accepted as Google Summer of Code Project. It is already on-par with the prior implementation feature-wise. Sorting is in reverse chronological order because usually people are most interested in the current state of affairs. Also fixes broken link that ended with

Re: wl_output ambiguity, xdg_shell fullscreen refresh rate

Am Dienstag, den 16.05.2017, 12:28 +0300 schrieb Pekka Paalanen: > On Mon, 15 May 2017 17:31:57 +0200 > Philipp Kerling <pkerl...@casix.org> wrote: > 2017-05-15 (月) の 11:18 +0300 に Pekka Paalanen さんは書きました: > > > On Sun, 14 May 2017 14:43:44 +0200 > > > Philipp K

Re: wl_output ambiguity, xdg_shell fullscreen refresh rate

Hi, Am Dienstag, den 16.05.2017, 11:30 +0300 schrieb Pekka Paalanen: > On Mon, 15 May 2017 17:51:16 +0200 > Philipp Kerling <pkerl...@casix.org> wrote: > > > 2017-05-15 (月) の 12:19 +0200 に Philipp Zabel さんは書きました: > > > On Mon, 2017-05-15 at 11:18 +0300, Pekka Paalan

Re: wl_output ambiguity, xdg_shell fullscreen refresh rate

2017-05-15 (月) の 12:19 +0200 に Philipp Zabel さんは書きました: > On Mon, 2017-05-15 at 11:18 +0300, Pekka Paalanen wrote: > > On Sun, 14 May 2017 14:43:44 +0200 > > Philipp Kerling <pkerl...@casix.org> wrote: > > >  * Am I correct in that if I use zxdg_tople

Re: wl_output ambiguity, xdg_shell fullscreen refresh rate

Thanks for your answers! See reply below. 2017-05-15 (月) の 11:18 +0300 に Pekka Paalanen さんは書きました: > On Sun, 14 May 2017 14:43:44 +0200 > Philipp Kerling <pkerl...@casix.org> wrote: > > To start off: > >  * Kodi should offer the user the opportunity to select inside the >