[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

Running multliple fullscreen applications on each of the the DRM connector

Currently I have a DRM modeset master which have multiple (HDMI) connectors. I suppose there is a limitation (or security feature) in DRM that only one user process can be a DRM master and only the master can do drmMode* operations. Wondering how to run multiple fullscreen applications (each for

Re: [PATCH wayland 2/3] scanner: Allow adding a prefix to exported symbols

On 27 July 2017 at 14:01, Pekka Paalanen wrote: > On Wed, 26 Jul 2017 16:09:32 +0100 > Emil Velikov wrote: > >> On 25 July 2017 at 10:24, Pekka Paalanen wrote: >> > On Tue, 25 Jul 2017 15:25:58 +0800 >> > Jonas Ådahl wrote: >> > >> >> On Mon, Jul 24, 2017 at 02:16:04PM +0300, Pekka Paalanen wro

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

On 7/28/17 2:11 PM, Philipp Kerling wrote: 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.

Re: [PATCH 5/5] wayland-scanner.mk: default --object-type to static

On 27 July 2017 at 14:34, Pekka Paalanen wrote: > On Wed, 26 Jul 2017 14:56:21 +0100 > Emil Velikov wrote: > >> From: Emil Velikov >> >> Unlike the core wayland library, it's recommended that one statically >> embeds the protocol within their binary. >> > > Hi, > > that is true, but I'd rather l

Re: [PATCH 4/5] build: set the scanner --object-type option

On 27 July 2017 at 14:36, Pekka Paalanen wrote: > On Wed, 26 Jul 2017 14:56:20 +0100 > Emil Velikov wrote: > >> From: Emil Velikov >> >> Unlike most other scanner users, the core wayland interfaces are >> public ally available via the libwayland DSO. >> >> Signed-off-by: Emil Velikov >> --- >>

Re: [PATCH 3/5] scanner: introduce --object-type option

On 27 July 2017 at 14:25, Pekka Paalanen wrote: > On Wed, 26 Jul 2017 14:56:19 +0100 > Emil Velikov wrote: > >> From: Emil Velikov >> >> The option is used to indicate how the code will be used - would it be a >> part of shared or static one. >> >> In the former case one needs to export the spec

[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 --- deskto

Re: [PATCH wayland 1/3] Pass input/output files as arguments to wayland-scanner

On 27 July 2017 at 13:53, Pekka Paalanen wrote: > On Wed, 26 Jul 2017 15:57:19 +0100 > Emil Velikov wrote: > >> On 3 July 2017 at 10:16, Jonas Ådahl wrote: >> > When input/output files are passed as arguments to wayland-scanner, >> > instead of using stdin/stdout, warning and error messages will

Re: [PATCH weston] libweston-desktop: fix the size of unmaximized xdg surfaces

2017-07-27 15:22 GMT+02:00 Quentin Glidic : > On 7/27/17 3:01 PM, Giulio Camuffo wrote: >> >> When unmaximizing a surface the configure event should send 0,0 as the >> requested size, so that the client can use the size that it had before >> maximizing > > > Hi, > > I disagree on this patch for a f