Xi: use public.processInputProc to replay the touch history
If a device is frozen in results to a grab, we need to enqueue the events. This makes things complicated, and hard to follow since touch events are now replayed in the history, pushed into EnqueueEvent, then replayed later during PlayReleasedEvents in response to an XAllowEvents. While the device is frozen, no touch events are processed, so if there is a touch client with ownership mask _below_ the grab this will delay the delivery and potentially screw gesture recognition. However, this is the behaviour we have already anyway if the top-most client is a sync pgrab or there is a sync grab active on the device when the TouchBegin was generated. (also note, such a client would only reliably work in case of ReplayPointer anyway) Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
This commit is contained in:
parent
214d11d3fc
commit
a7d989d335
|
@ -1554,7 +1554,7 @@ ProcessTouchEvent(InternalEvent *ev, DeviceIntPtr dev)
|
|||
|
||||
touchid = ev->device_event.touchid;
|
||||
|
||||
if (type == ET_TouchBegin) {
|
||||
if (type == ET_TouchBegin && !(ev->device_event.flags & TOUCH_REPLAYING)) {
|
||||
ti = TouchBeginTouch(dev, ev->device_event.sourceid, touchid,
|
||||
emulate_pointer);
|
||||
}
|
||||
|
@ -1621,7 +1621,9 @@ ProcessTouchEvent(InternalEvent *ev, DeviceIntPtr dev)
|
|||
* called after event type mutation. Touch end events are always processed
|
||||
* in order to end touch records. */
|
||||
/* FIXME: check this */
|
||||
if ((type == ET_TouchBegin && !TouchBuildSprite(dev, ti, ev)) ||
|
||||
if ((type == ET_TouchBegin &&
|
||||
!(ev->device_event.flags & TOUCH_REPLAYING) &&
|
||||
!TouchBuildSprite(dev, ti, ev)) ||
|
||||
(type != ET_TouchEnd && ti->sprite.spriteTraceGood == 0))
|
||||
return;
|
||||
|
||||
|
@ -1629,7 +1631,7 @@ ProcessTouchEvent(InternalEvent *ev, DeviceIntPtr dev)
|
|||
/* WARNING: the event type may change to TouchUpdate in
|
||||
* DeliverTouchEvents if a TouchEnd was delivered to a grabbing
|
||||
* owner */
|
||||
DeliverTouchEvents(dev, ti, (InternalEvent *) ev, 0);
|
||||
DeliverTouchEvents(dev, ti, ev, ev->device_event.resource);
|
||||
if (ev->any.type == ET_TouchEnd)
|
||||
TouchEndTouch(dev, ti);
|
||||
|
||||
|
|
16
dix/touch.c
16
dix/touch.c
|
@ -474,7 +474,21 @@ TouchEventHistoryReplay(TouchPointInfoPtr ti, DeviceIntPtr dev, XID resource)
|
|||
DeviceEvent *ev = &ti->history[i];
|
||||
|
||||
ev->flags |= TOUCH_REPLAYING;
|
||||
DeliverTouchEvents(dev, ti, (InternalEvent *) ev, resource);
|
||||
ev->resource = resource;
|
||||
/* FIXME:
|
||||
We're replaying ti->history which contains the TouchBegin +
|
||||
all TouchUpdates for ti. This needs to be passed on to the next
|
||||
listener. If that is a touch listener, everything is dandy.
|
||||
If the TouchBegin however triggers a sync passive grab, the
|
||||
TouchUpdate events must be sent to EnqueueEvent so the events end
|
||||
up in syncEvents.pending to be forwarded correctly in a
|
||||
subsequent ComputeFreeze().
|
||||
|
||||
However, if we just send them to EnqueueEvent the sync'ing device
|
||||
prevents handling of touch events for ownership listeners who
|
||||
want the events right here, right now.
|
||||
*/
|
||||
dev->public.processInputProc((InternalEvent*)ev, dev);
|
||||
}
|
||||
}
|
||||
|
||||
|
|
|
@ -123,6 +123,7 @@ struct _DeviceEvent {
|
|||
int corestate; /**< Core key/button state BEFORE the event */
|
||||
int key_repeat; /**< Internally-generated key repeat event */
|
||||
uint32_t flags; /**< Flags to be copied into the generated event */
|
||||
uint32_t resource; /**< Touch event resource, only for TOUCH_REPLAYING */
|
||||
};
|
||||
|
||||
/**
|
||||
|
|
Loading…
Reference in New Issue