Re: [PATCH weston v2 2/2] libweston-desktop/xdg-shell: Properly handle ack_configure

2017-07-19 Thread Jonas Ã…dahl
On Tue, Jul 18, 2017 at 01:14:49PM +0200, Quentin Glidic wrote: > From: Quentin Glidic > > Now we keep track of serial->state association and we discard the states > that the client ignored. > > Signed-off-by: Quentin Glidic > --- > libweston-desktop/xdg-shell-v5.c | 45 +++

Re: [PATCH weston 1/2] text-backend: Allow client hiding of input panel

2017-07-19 Thread Silvan Jegen
On Wed, Jul 19, 2017 at 3:49 PM, Joshua Watt wrote: > On Sun, 2017-07-09 at 21:26 +0200, Silvan Jegen wrote: >> Hi Joshua >> >> On Wed, Jul 05, 2017 at 08:58:51AM -0500, Joshua Watt wrote: >> > On Sat, 2017-06-24 at 16:03 -0500, Joshua Watt wrote: >> > > Previously, the hide_input_panel and show_i

Re: [PATCH weston v11 03/13] compositor-drm: Add DRM property cache

2017-07-19 Thread Pekka Paalanen
On Tue, 18 Jul 2017 14:14:25 +0100 Daniel Stone wrote: > Add a cache for DRM property IDs and values, and use it for the two > connector properties we currently update: DPMS and EDID. > > As DRM property ID values are not stable, we need to do a name -> ID > lookup each run in order to discover

Re: [PATCH weston 1/2] text-backend: Allow client hiding of input panel

2017-07-19 Thread Joshua Watt
On Sun, 2017-07-09 at 21:26 +0200, Silvan Jegen wrote: > Hi Joshua > > On Wed, Jul 05, 2017 at 08:58:51AM -0500, Joshua Watt wrote: > > On Sat, 2017-06-24 at 16:03 -0500, Joshua Watt wrote: > > > Previously, the hide_input_panel and show_input_panel messages > > > for > > > the text > > > input pr

Re: [PATCH weston v11 01/13] compositor-drm: Refactor sprite create/destroy into helpers

2017-07-19 Thread Pekka Paalanen
On Tue, 18 Jul 2017 14:14:23 +0100 Daniel Stone wrote: > From: Pekka Paalanen > > This moves the single sprite creation code from create_sprites() into a > new function. The readability clean-up is small, but my intention is to > write an alternate version of create_sprites(), and sharing the s

[PATCH v4] Add xdg-output protocol

2017-07-19 Thread Olivier Fourdan
This protocol aims at describing outputs in way which is more in line with the concept of an output on desktop oriented systems. Some information are more specific to the concept of an output for a desktop oriented system and may not make sense in other applications, such as IVI systems for exampl