Extend touch events.
authorLaszlo Agocs <laszlo.p.agocs@nokia.com>
Sun, 27 Nov 2011 15:42:23 +0000 (17:42 +0200)
committerQt by Nokia <qt-info@nokia.com>
Fri, 9 Dec 2011 13:15:37 +0000 (14:15 +0100)
commit4222603f8ea3a0d0ef5b9a190605ad86e00f27f6
tree2ace610731b845e4e04e6ea8f0def0ce3aee31a4
parent2c4879a7676d6a75379ac6ff24ac4c2a6c2b9658
Extend touch events.

The capability flags indicate which information is valid in the touch
points. Previously there was no way to tell if e.g. the value returned
by pressure() is actually the value provided by the driver/device or
it is just something bogus due to pressure not being supported.

The points' flags return information about the individual touch
points. One use case is to differentiate between touches made by
finger and pen.

Velocity, if available, is now also exposed.

Each touch point can now contain an additional list of "raw"
positions. These points are not reported individually but are taken
into account in some way by the underlying device and drivers to
generate the final, "accurate" touch point. In case the underlying
drivers expose these additional positions, they are made available in
the lists returned by the touch points' rawScreenPosition().

The raw positions are only available in screen coordinates to prevent
wasting time with mapping from global positions in applications that
do not use this data. Instead, apps can query the QWindow to which the
touch event was sent via QTouchEvent::window() and can call
mapFromGlobal() manually if they need local raw positions.

The capability and device type information is now held in a new
QTouchDevice class. Each touch event will contain only a pointer to
one of the global QTouchDevice instances. On top of type and
capability, the new class also contains a name which can be used to
differentiate between multiple touch input devices (i.e. to tell from
which one a given QTouchEvent originates from).

The introduction of QTouchDevice has three implications: The
QTouchEvent constructor and QWindowSystemInterface::handleTouchEvent
need to be changed (to pass a QTouchDevice pointer instead of merely a
device type value), and each platform or generic plug-in is now
responsible for registering one or more devices using the new API
QWindowSystemInterface::registerTouchDevice.

Change-Id: Ic1468d3e43933d8b5691d75aa67c43e1bc7ffe3e
Reviewed-by: Lars Knoll <lars.knoll@nokia.com>
30 files changed:
dist/changes-5.0.0
src/gui/kernel/kernel.pri
src/gui/kernel/qevent.cpp
src/gui/kernel/qevent.h
src/gui/kernel/qevent_p.h
src/gui/kernel/qguiapplication.cpp
src/gui/kernel/qtouchdevice.cpp [new file with mode: 0644]
src/gui/kernel/qtouchdevice.h [new file with mode: 0644]
src/gui/kernel/qtouchdevice_p.h [new file with mode: 0644]
src/gui/kernel/qwindowsysteminterface_qpa.cpp
src/gui/kernel/qwindowsysteminterface_qpa.h
src/gui/kernel/qwindowsysteminterface_qpa_p.h
src/plugins/generic/touchscreen/qtoucheventsenderqpa.cpp
src/plugins/generic/touchscreen/qtoucheventsenderqpa.h
src/plugins/platforms/cocoa/qnsview.mm
src/plugins/platforms/windows/qwindowsmousehandler.cpp
src/plugins/platforms/windows/qwindowsmousehandler.h
src/plugins/platforms/xcb/qxcbconnection_maemo.cpp
src/testlib/qtesttouch.h
src/widgets/graphicsview/qgraphicsscene.cpp
src/widgets/kernel/qapplication.cpp
src/widgets/kernel/qapplication_p.h
src/widgets/kernel/qwidget.cpp
src/widgets/kernel/qwidgetwindow_qpa.cpp
src/widgets/util/qflickgesture.cpp
tests/auto/gui/kernel/qtouchevent/tst_qtouchevent.cpp
tests/auto/other/gestures/tst_gestures.cpp
tests/auto/widgets/graphicsview/qgraphicsitem/tst_qgraphicsitem.cpp
tests/auto/widgets/kernel/qapplication/tst_qapplication.cpp
tests/auto/widgets/util/qscroller/tst_qscroller.cpp