iOS: Remove sending of duplicate touch events after broken merge
The merge in 0f315adf91 resulted in keeping both code paths,
in effect sending two touch events for each native touch event,
and also re-introduced the bug fixed by sending the touch events
asynchronously in some cases.
Change-Id: Id81f02d9597f4e0baeaddbdf9057fa32b6c31b2f
Reviewed-by: Frederik Gladhorn <frederik.gladhorn@qt.io>
Reviewed-by: Lars Knoll <lars.knoll@qt.io>
bb10
parent
32d9cf7310
commit
49a760e454
|
|
@ -439,7 +439,7 @@ Q_LOGGING_CATEGORY(lcQpaTablet, "qt.qpa.input.tablet")
|
|||
}
|
||||
if (m_activeTouches.isEmpty())
|
||||
return;
|
||||
QWindowSystemInterface::handleTouchEvent<QWindowSystemInterface::SynchronousDelivery>(m_qioswindow->window(), timeStamp, iosIntegration->touchDevice(), m_activeTouches.values());
|
||||
|
||||
if (!static_cast<QUIWindow *>(self.window).sendingEvent) {
|
||||
// The event is likely delivered as part of delayed touch delivery, via
|
||||
// _UIGestureEnvironmentSortAndSendDelayedTouches, due to one of the two
|
||||
|
|
|
|||
Loading…
Reference in New Issue