On 05/12/2016 17:00, Pekka Paalanen wrote:
On Mon, 5 Dec 2016 16:48:38 +0100
Quentin Glidic wrote:
On 05/12/2016 16:29, Pekka Paalanen wrote:
On Mon, 11 Jul 2016 11:29:40 +0200
Quentin Glidic wrote:
From: Quentin Glidic
Currently, layers’ order depends on the module loading order and i
On 05/12/2016 16:48, Quentin Glidic wrote:
On 05/12/2016 16:29, Pekka Paalanen wrote:
On Mon, 11 Jul 2016 11:29:40 +0200
Quentin Glidic wrote:
From: Quentin Glidic
>>> [snip]
+ */
+WL_EXPORT void
+weston_layer_set_position(struct weston_layer *layer,
+ enum weston_layer_positi
From: Quentin Glidic
Currently, layers’ order depends on the module loading order and it does
not survive runtime modifications (like shell locking/unlocking).
With this patch, modules can safely add their own layer at the expected
position in the stack, with runtime persistence.
Signed-off-by:
Carsten Haitzler (The Rasterman) wrote:
> On Tue, 13 Dec 2016 17:46:25 +1100 Graeme Gill said:
> a display may not have a single native colorspace. it may be able to switch.
> embedded devices can do this as the display panel may have extra control lines
> for switching to a different display ga
