• Peter Hutterer's avatar
    Post a motion event after proximity events · 8bc69459
    Peter Hutterer authored
    This patch splits the meat of xf86libinput_handle_tablet_axis into a helper
    function xf86libinput_post_tablet_motion(), to be called right after we send
    the proximity in event.
    Clients that don't handle proximity (e.g. all XI2 clients) don't see the
    coordinates we send along with the proximity events. And, for historical
    reasons, they may not look at the coordinates in button events. So a device
    that comes into proximity and immediately sends a tip down button event
    doesn't send a motion event, causing the client to think the tip down was at
    whatever the last known position was (before previous prox-out).
    The practical effect is that when a user tries to draw a few dots, they end up
    being connected to each other.
    https://bugzilla.redhat.com/show_bug.cgi?id=1433755Signed-off-by: Peter Hutterer's avatarPeter Hutterer <peter.hutterer@who-t.net>
Last commit
Last update
Makefile.am Loading commit data...
bezier.c Loading commit data...
bezier.h Loading commit data...
draglock.c Loading commit data...
draglock.h Loading commit data...
xf86libinput.c Loading commit data...