From 5a6fc53acc3721b637453ab5a7b36cb36db97821 Mon Sep 17 00:00:00 2001 From: Giulio Camuffo Date: Mon, 14 Apr 2014 12:39:05 +0300 Subject: Make it possible to have custom shell implementations Different compositors may need different shell behaviors, or even different shell protocols. A smartphone compositor, for example, may want to make wl_shell_surface::set_popup or other requests noop, because they don't make sense in the formfactor, or it may even want to not implement wl_shell_surface at all, but some smartphone_shell_surface. A compositor may define its own shell implementation by overriding QWaylandCompositor::initShell(), and creating there its interface instance. The default implementation still creates the built-in wl_shell_surface implementation. Change-Id: I143b0cd4e30e31d4051ada6e562d486d9bf1a751 Reviewed-by: Gunnar Sletta --- examples/qml-compositor/WindowContainer.qml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'examples') diff --git a/examples/qml-compositor/WindowContainer.qml b/examples/qml-compositor/WindowContainer.qml index 8d25327cc..f1b212094 100644 --- a/examples/qml-compositor/WindowContainer.qml +++ b/examples/qml-compositor/WindowContainer.qml @@ -182,7 +182,7 @@ Item { onUnmapped: unmapAnimation.start() } Connections { - target: container.child + target: container.child ? container.child : null onSurfaceDestroyed: { destroyAnimation.start(); } -- cgit v1.2.3