From: Pekka Paalanen <[email protected]> Commit a30e29af2e4d0ad6fc476ae7cc13c4cad5119217 introduced the code to deal with a touchscreen with touches already down when Weston starts using it. It fixed the touchpoint counting problem.
However, Weston still should not forward or process the unmatched touch-ups either. Code inspection says it would confuse the idle-inhibit counting, and it could probably confuse clients as well. Hence, just drop unmatched touch-ups. Enhance the warning message to allow identifying where the event came from. v2: - use syspath instead of devpath Signed-off-by: Pekka Paalanen <[email protected]> v1 Reviewed-by: Peter Hutterer <[email protected]> v1 Tested-by: Matt Hoosier <[email protected]> --- libweston/input.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/libweston/input.c b/libweston/input.c index 6816cc32..5bea691a 100644 --- a/libweston/input.c +++ b/libweston/input.c @@ -2458,8 +2458,9 @@ notify_touch_normalized(struct weston_touch_device *device, * more fingers on the touch screen, in which * case we didn't get the corresponding down * event. */ - weston_log("unmatched touch up event\n"); - break; + weston_log("Unmatched touch up event on seat %s, device %s\n", + seat->seat_name, device->syspath); + return; } weston_compositor_idle_release(seat->compositor); -- 2.16.1 _______________________________________________ wayland-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/wayland-devel
