libweston: Position layers in an absolute way
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. v4 Reviewed-by: Giulio Camuffo <giuliocamuffo@gmail.com> Signed-off-by: Quentin Glidic <sardemff7+git@sardemff7.net> Acked-by: Daniel Stone <daniels@collabora.com> [Pekka: fix three whitespace issues] Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.co.uk>
This commit is contained in:
committed by
Pekka Paalanen
parent
39d7e99a46
commit
82681571cf
@@ -912,7 +912,9 @@ module_init(struct weston_compositor *compositor,
|
||||
|
||||
shell->client_destroyed.notify = client_destroyed;
|
||||
|
||||
weston_layer_init(&shell->layer, &compositor->cursor_layer.link);
|
||||
weston_layer_init(&shell->layer, compositor);
|
||||
weston_layer_set_position(&shell->layer,
|
||||
WESTON_LAYER_POSITION_FULLSCREEN);
|
||||
|
||||
wl_list_init(&shell->output_list);
|
||||
shell->output_created_listener.notify = output_created;
|
||||
|
||||
Reference in New Issue
Block a user