summaryrefslogtreecommitdiffstats
path: root/examples
diff options
context:
space:
mode:
authorGiulio Camuffo <giulio.camuffo@jollamobile.com>2014-04-14 12:39:05 +0300
committerThe Qt Project <gerrit-noreply@qt-project.org>2014-04-29 12:07:02 +0200
commit5a6fc53acc3721b637453ab5a7b36cb36db97821 (patch)
treec7d645f9f2e8bf3c83ef4883e37c06ac611cb08e /examples
parent89bb266aa84bc8fa742999c99e47c3fed742c6a9 (diff)
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 <gunnar.sletta@jollamobile.com>
Diffstat (limited to 'examples')
-rw-r--r--examples/qml-compositor/WindowContainer.qml2
1 files changed, 1 insertions, 1 deletions
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();
}