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 1190

Summary: Resuming an app on retina displays, messes up resolution setting.
Product: SDL Reporter: Jeremy Jurksztowicz <jurksztowicz>
Component: videoAssignee: Ryan C. Gordon <icculus>
Status: RESOLVED FIXED QA Contact: Sam Lantinga <slouken>
Severity: major    
Priority: P1 Keywords: target-2.0.0
Version: HG 2.0   
Hardware: iPhone/iPod touch   
OS: iOS (All)   

Description Jeremy Jurksztowicz 2011-04-27 17:49:12 UTC 
In the UIKit_GetDisplayModes function in SDL_uikitvideo.m, you grab an NSArray of modes using UIScreen -availableModes. This array has only ONE entry, that is the retina display native mode of 640x960. Later on when restoring the screen in the SDL_GetClosestDisplayModeForDisplay function it can't find the QVGA mode because it was never added.

POSSIBLE  SOLUTION: Hardcode QVGA into UIKit_GetDisplayModes.
Comment 1 Sam Lantinga 2012-01-06 22:44:46 UTC 
I'm reassigning this to Ryan since he's going to look into retina display support.
Comment 2 Sam Lantinga 2013-05-21 02:35:59 UTC 
I believe this is fixed in the current snapshot:
http://www.libsdl.org/tmp/SDL-2.0.zip

Please reopen this bug if that isn't the case.

Thanks!
Comment 3 Ryan C. Gordon 2013-07-12 18:52:36 UTC 
(Sorry if you get a lot of copies of this email, we're touching dozens of bug reports right now.)

Tagging a bunch of bugs as target-2.0.0, Priority 1.

This means we're in the final stretch for an official SDL 2.0.0 release! These are the bugs we really want to fix before shipping if humanly possible.

That being said, we don't promise to fix them because of this tag, we just want to make sure we don't forget to deal with them before we bless a final 2.0.0 release, and generally be organized about what we're aiming to ship.

Hopefully you'll hear more about this bug soon. If you have more information (including "this got fixed at some point, nevermind"), we would love to have you come add more information to the bug report when you have a moment.

Thanks!
--ryan.
Comment 4 Sam Lantinga 2013-07-27 05:33:46 UTC 
No response in two years, and I haven't seen any other reports of this recently.  Closing for now.

Jeremy, please reopen this bug if you are still having this problem.