diff options
author | Shawn Rutledge <shawn.rutledge@qt.io> | 2020-09-30 13:51:59 +0200 |
---|---|---|
committer | Shawn Rutledge <shawn.rutledge@qt.io> | 2021-01-04 18:03:52 +0000 |
commit | e203a185cfab199a89a33b903096d6d0023a8a88 (patch) | |
tree | 841fa0a318a6ef8f5ce288a4f998a6ffa290dd48 /examples/qml/xmlhttprequest/GetForm.ui.qml | |
parent | 35614462443c100b6753b335b58a134fed4b5c35 (diff) |
doc: explain QQItem event delivery, handlers, setAcceptTouchEvents()
We quietly recommended calling setAcceptTouchEvents() in the Qt 5.10
release notes in any Item subclass that wants to receive touch events,
and in the docs for setAcceptTouchEvents() itself; but the message about
the impending behavior change might not have been obvious enough.
In Qt 6 it becomes mandatory, so clearer docs will hopefully help to
stave off bogus bug reports.
We also never had a great overview of event handling from an Item's
perspective; now it's a little better.
Followup to ab91e7fa02a562d80fd0747f28a60e00c3b45a01 and
a97759a336c597327cb82eebc9f45c793aec32c9
[ChangeLog][QtQuick][QQuickItem] When subclassing QQuickItem, you
should call setAcceptTouchEvents(true) if you need the item to receive
touch events. It will be required in Qt 6.
Task-number: QTBUG-87018
Task-number: QTBUG-87082
Change-Id: I1c7a43979e3665778d61949c9d37c1d085ed594b
Reviewed-by: Volker Hilsheimer <volker.hilsheimer@qt.io>
(cherry picked from commit 7c648280bb53c4276ba4ae2abf26d070fedde71a)
Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io>
Diffstat (limited to 'examples/qml/xmlhttprequest/GetForm.ui.qml')
0 files changed, 0 insertions, 0 deletions