Begin handling the QEvent refactoring

This is an intermediate step to get Qt Quick working again after
qtbase 4e400369c08db251cd489fec1229398c224d02b4.

- QQuickEventPoint::id() is no longer unique across devices, because now
  eventPoint.event.device tells which specific device the event comes from.
  (In Qt 5, we could not yet add the device pointer to QInputEvent.)
- However, MultiPointTouchArea's docs say that each pointId is unique,
  and so do the HandlerPoint docs (for similar use cases with PointHandler).
  So we still need the same hack using a Qt-specific short device ID
  to unique-ify the QEventPoint::id(). Now we use the device index
  in QInputDevice::devices() as the short ID.
- Otherwise, we trust QInputDevice::systemId() and QEventPoint::id()
  more than before.
- Use QMutable* classes from qevent_p.h to continue using setters
  that were in QTouchEvent before, etc.  But setTouchPoints() is
  not there, so we have to make new event instances in a couple of cases.
- QGuiApplicationPrivate::setMouseEventCapsAndVelocity() and
  setMouseEventSource() are gone.
- Use (compiler-written) event copy constructors when possible.

Task-number: QTBUG-72173
Change-Id: I3915dc535ae4c5a81cbf333aba9355f01c420c15
Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io>

0 files changed, 0 insertions, 0 deletions