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 918 - Touchscreen Bug with ScummVM
Summary: Touchscreen Bug with ScummVM
Status: RESOLVED WONTFIX
Alias: None
Product: SDL
Classification: Unclassified
Component: *don't know* (show other bugs)
Version: HG 2.1
Hardware: x86 Windows 7
: P2 major
Assignee: Ryan C. Gordon
QA Contact: Sam Lantinga
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-12-29 16:07 UTC by blubbing.blub
Modified: 2013-05-21 01:11 UTC (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description blubbing.blub 2009-12-29 16:07:25 UTC 
ScummVM doesn't seem to be able to use the Touchscreen of my MID (Viliv
X70) correctly, and since ScummVM uses SDL, they told me to file a bug report here.
Everything works fine in window mode, but if i switch to fullscreen the
mouse pointer sticks in the top left edge.
It happens both in the ScummVM launcher and the Game (Beneath a steel
Sky).
I think it has something to do with the absolute positioning of the cursor
on a touchscreen device.
Comment 1 Sam Lantinga 2010-01-26 21:22:03 UTC 
This will probably be resolved by your mouse input revamp, Ryan.
Comment 2 Sam Lantinga 2010-01-26 21:22:39 UTC 
Whoops, I merely meant to assign this, not assume it's already fixed. :)
Comment 3 dma 2010-03-21 02:05:42 UTC 
I also get this problem on my MID (Umid mbook m1), when using SDL based software like GrafX2, Hatari, or Protrekkr.
Comment 4 Sam Lantinga 2011-01-20 17:34:57 UTC 
I believe mouse input has been fixed on Windows, can you retest with the latest snapshot?

Thanks!
Comment 5 dma 2011-07-10 10:11:14 UTC 
Sorry, but it still doesn't work.
Comment 6 Sam Lantinga 2013-05-21 01:11:39 UTC 
We don't have access to these devices and no way of testing them.  Please feel free to reopen the bug if you have a patch that works for you.