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
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 it does
> >> not survi
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 it does
not survive runtime modifications (like shell locking/unlocking).
With this patch, modules can saf
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 it does
> not survive runtime modifications (like shell locking/unlocking).
> With this patch, modules can safely add their own layer at the expec
2016-07-11 11:29 GMT+02:00 Quentin Glidic :
> 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 i
Hi Quentin,
On 11 July 2016 at 10:29, Quentin Glidic
wrote:
> 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 st
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: