On an embedded device I have Wayland and Weston working fine with my touchscreen. After calibration I am able to use apps such as weston-simple-touch but Qt 5 using Wayland doesn't recognize any touch inputs (connecting a mouse works fine).
To fix my Qt 5 (QtWayland) issue I switched to using the latest version of Weston , Wayland and QtWayland and I saw the same behavior as I saw before. Based on bugs filed by other people it seems I needed Weston to send WL_TOUCH_FRAME which the latest Weston doesn't send but the latest libinput currently supports. I rebuilt Weston with "--enable-libinput-backend" and built and installed the latest libinput and now touch isn't working with Wayland/Weston. I did alot of debugging and currently I know that libinput is properly recognizing and passing my touch messages to Weston. Weston is currently recognizing the touch messages. However, in src/input.c (Weston) notify_touch is receiving the proper WL_TOUCH_DOWN,WL_TOUCH_MOTION and WL_TOUCH_UP events. WL_TOUCH_DOWN after detecting the first touch point calls weston_compositor_pick_view but null is always returned. This null view is then passed to weston_touch_set_focus which associates null with the seat. When moving your finger WL_TOUCH_MOTION is processed within notify_touch and it tries to retrieve the current view that is in focus "ev = touch->focus". However due to the previous call to weston_touch_set_focus their is no current view in focus so the break statement is executed which means the motion event isn't processed. So the inability to determine which view is being focused on is what causing my touch inputs not to be passed to the app such as weston-simple-touch. What I don't understand is why am I not having this problem when switching to libinput when without it atleast Wayland and Weston is working correctly? Any suggestions on how to debug this issue any further?
_______________________________________________ wayland-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/wayland-devel
