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 1476

Summary: Touchscreen mouse clicking positioned incorrectly
Product: SDL Reporter: quinnquinn10
Component: eventsAssignee: Sam Lantinga <slouken>
Status: RESOLVED ENDOFLIFE QA Contact: Sam Lantinga <slouken>
Severity: normal    
Priority: P2    
Version: 1.2.14   
Hardware: x86   
OS: Windows (All)   

Description quinnquinn10 2012-04-14 20:05:57 UTC 
Using a Gigabyte T1005 with capactive touch screen, windows 7 and the standard HID drivers. The drivers convert the touchscreen interaction into mouse events.

Basic logging of SDL_MOUSEMOTION, SDL_MOUSEBUTTONDOWN, SDL_MOUSEBUTTONUP show that the mouse down/up events are received by the application code prior to any mouse motion event and have stale x,y coordinates. Calling SDL_GetMouseState when handling the mouse down/up event returns the correct coordinates.

Replacing the 1.2.14 DLL with the previous 1.2.13 DLL corrects the problem.

I'm guessing the 'Improved mouse input responsiveness for first-person-shooter games' in the 1.2.14 release note may have involved queuing mouse down/up events before other events including mouse movement events and caused this issue.

Workaround:
Use SDL_GetMouseState to correct click coordinates on a mouse down/up event.
Comment 1 Ryan C. Gordon 2015-08-25 09:38:21 UTC 
Hello, and sorry if you're getting several copies of this message by email, since we are closing many bugs at once here.

We have decided to mark all SDL 1.2-related bugs as RESOLVED ENDOFLIFE, as we don't intend to work on SDL 1.2 any further, but didn't want to mark a large quantity of bugs as RESOLVED WONTFIX, to clearly show what was left unattended to and make it easily searchable.

Our current focus is on SDL 2.0.

If you are still having problems with an ENDOFLIFE bug, your absolute best option is to move your program to SDL2, as it will likely fix the problem by default, and give you access to modern platforms and tons of super-cool new features.

Failing that, we _will_ accept small patches to fix these issues, and put them in revision control, although we do not intend to do any further official 1.2 releases.

Failing that, please feel free to contact me directly by email (icculus@icculus.org) and we'll try to find some way to help you out of your situation.

Thank you,
--ryan.