fail to receive touch_frame after final touch_up (Qt)
Submitted by Shawn Rutledge
Assigned to Wayland bug list
In Qt applications it was not possible to press any QPushButton or QtQuick MouseArea on a touchscreen because of this: it waits for the release in order to treat the press-release sequence as a "click". So we added a workaround: if all touch points have been released, send ourselves an artificial touch_frame. But it has been said that this might be a regression after the latest work with wayland using libinput.
Tested with the latest git versions of wayland, weston and libinput on Arch Linux, on two different systems both with touchscreens.