summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorBernd Weimer <bernd.weimer@qt.io>2022-11-15 16:38:43 +0100
committerBernd Weimer <bernd.weimer@qt.io>2022-12-01 14:35:32 +0100
commita7d4f5324b3e80f794a73bbb4f2f4674214cf4a5 (patch)
treed16fd7abe6c5e7e6ebec02cf4841e7645d19f585 /doc
parent68888133e2aa7dd3ed2ef1c4d1095065749d7e7f (diff)
downloadqtapplicationmanager-a7d4f5324b3e80f794a73bbb4f2f4674214cf4a5.tar.gz
Forward keyboard focus to applications
Key events were not passed to applications, when the focus moved to a WindowItem in the System UI, since the item representing the application window is actually a child of the WindowItem. A possible solution would be to explicitly send the key events to the application item, though the approach taken here is to forward the keyboard focus. This results in key events always reaching the application first (even when the System UI would actually consume the events) and in single-process mode, if the application consumes the event the System UI won't get it any more. Fixes: QTBUG-108837 Change-Id: I1699556f1a67057e8be2848e37c846c2ee33a646 Reviewed-by: Robert Griebl <robert.griebl@qt.io>
Diffstat (limited to 'doc')
-rw-r--r--doc/singlevsmultiprocess.qdoc10
1 files changed, 10 insertions, 0 deletions
diff --git a/doc/singlevsmultiprocess.qdoc b/doc/singlevsmultiprocess.qdoc
index 732ebd75..e09e2944 100644
--- a/doc/singlevsmultiprocess.qdoc
+++ b/doc/singlevsmultiprocess.qdoc
@@ -160,6 +160,16 @@ compatibility. The following are some examples:
\endlist
+\section1 Input
+
+There are some peculiarities in terms of keyboard input, caused amongst others by the fact, that
+Wayland clients (applications) cannot report back to the System UI, whether they have accepted a
+key event. In multi-process mode key events will be passed to both, the System UI and applications.
+This is also the case in single-process mode, however, if the application accepts the event, the
+System UI will not get it any more. This can be circumvented by using \l{Shortcut}s or installing a
+global event filter in the System UI.
+
+
\section1 Resource Consumption
CPU usage on a multi-core system may be more efficient in multi-process mode, since the OS can