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 1437 - SDL_SetVideoMode sometimes does not change allowed mouse coordinates
Summary: SDL_SetVideoMode sometimes does not change allowed mouse coordinates
Status: RESOLVED ENDOFLIFE
Alias: None
Product: SDL
Classification: Unclassified
Component: video (show other bugs)
Version: 1.2.14
Hardware: x86 Linux
: P2 minor
Assignee: Sam Lantinga
QA Contact: Sam Lantinga
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-03-01 12:20 UTC by Mark Boyd
Modified: 2015-08-25 09:38 UTC (History)
0 users

See Also:


Attachments
Example program (442 bytes, text/plain)
2012-03-01 12:21 UTC, Mark Boyd
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Mark Boyd 2012-03-01 12:20:29 UTC
Mouse does not work properly after 2 calls to SDL_SetVideoMode.

I'm attaching a program which shows the problem (about 9 times out of 10 for me)
Move the mouse around inside the SDL window.  The window is 640x400 as it should be but the mouse coordinates never go past (319,199).  It looks like SDL_GetMouseState still thinks the window is 320x200.

If I uncomment the 1-second delay, the problem goes away.
Comment 1 Mark Boyd 2012-03-01 12:21:26 UTC
Created attachment 832 [details]
Example program
Comment 2 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.