We are currently migrating Bugzilla to GitHub issues.
Any changes made to the bug tracker now will be lost, so please do not post new bugs or make changes to them.
When we're done, all bug URLs will redirect to their equivalent location on the new bug tracker.

Bug 4238 - Touch screen taps on laptop cause which=0 mouse down events, instead of which=SDL_TOUCH_MOUSEID
Summary: Touch screen taps on laptop cause which=0 mouse down events, instead of which...
Status: RESOLVED WORKSFORME
Alias: None
Product: SDL
Classification: Unclassified
Component: *don't know* (show other bugs)
Version: 2.0.8
Hardware: x86_64 Linux
: P2 major
Assignee: Ryan C. Gordon
QA Contact: Sam Lantinga
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-08-24 17:58 UTC by Ellie
Modified: 2020-03-18 12:47 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ellie 2018-08-24 17:58:17 UTC
On this Linux laptop, touch screen taps on the laptop screen cause which=0 mouse down events, instead of which=SDL_TOUCH_MOUSEID. This has the potential to wreck havoc on touch input handling for any application that does its own touch processing (which I wanted to do), since this effectively makes it hard (impossible?) to tell apart regular mouse clicks and touch taps.

Hardware: Thinkpad Yoga 260
OS: GNU/Linux Fedora 28
Desktop: GNOME 3.28.2 (Xorg Session, not the default Wayland session)
Comment 1 Ellie 2018-08-25 17:06:47 UTC
I investigated this some more, and I'm not getting touch events AT ALL - every touch is just a which:0, button:1 mouse down. This is with SDL2 as provided by Fedora. Is this potentially some compilation issue, with some extension required for proper touch processing not compiled in?
Comment 2 Ellie 2018-09-29 15:19:31 UTC
I now filed a Fedora bug report here, since I don't know if this potentially a packaging issue: https://bugzilla.redhat.com/show_bug.cgi?id=1634291
Comment 3 Ellie 2020-03-18 12:47:53 UTC
I haven't seen this for a while, so maybe it was fixed on Fedora's side