diff options
author | Laszlo Agocs <laszlo.p.agocs@nokia.com> | 2012-01-13 08:22:47 +0200 |
---|---|---|
committer | Qt by Nokia <qt-info@nokia.com> | 2012-01-13 13:23:20 +0100 |
commit | 77cfaf1f2cfa05c502652716b52aced17c23ec2e (patch) | |
tree | 048865e3c9901ef1e490536bc1e943518c4547d1 /src/plugins | |
parent | 952df2ffd6e081748837a91dc32d14aa61449e2b (diff) |
Update touchscreen plug-in's readme
To match the new mouse-for-unhandled-touch-event feature in
QGuiApplication.
Change-Id: Ifa3872ab51a8e95bee235a3681b0a9d1ec13081c
Reviewed-by: Samuel Rødal <samuel.rodal@nokia.com>
Diffstat (limited to 'src/plugins')
-rw-r--r-- | src/plugins/generic/touchscreen/README | 8 |
1 files changed, 3 insertions, 5 deletions
diff --git a/src/plugins/generic/touchscreen/README b/src/plugins/generic/touchscreen/README index 6bd244df19..ac73f5f147 100644 --- a/src/plugins/generic/touchscreen/README +++ b/src/plugins/generic/touchscreen/README @@ -20,11 +20,9 @@ screen. If this is not desired, pass force_window in the plugin specification as shown in the example above. This will cause mapping the touch surface to the active window instead. -Only touch events are generated, mouse events are not. This is because -on desktop the touch device will usually act as a single-point mouse -replacement by default. For embedded systems the code could to be -extended to generate also mouse events (by calling handleMouseEvent -for the primary touch point for example). +Only touch events are generated, mouse events are not. Be aware however +that ignored touch events will generate a mouse event from the first +touch point by default. See AA_SynthesizeMouseForUnhandledTouchEvents. (2) Using in a compositor |