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 125

Summary: full screen problems in windib/windx drivers
Product: SDL Reporter: Sam Lantinga <slouken>
Component: videoAssignee: Ryan C. Gordon <icculus>
Status: RESOLVED WORKSFORME QA Contact: Sam Lantinga <slouken>
Severity: normal    
Priority: P2    
Version: don't know   
Hardware: x86   
OS: Windows (All)   

Description Sam Lantinga 2006-01-31 11:27:23 UTC 
Date: Wed, 04 Jan 2006 22:20:12 +0100
From: Manuel Bilderbeek <manuel@msxnet.org>
To: sdl@libsdl.org
Subject: [SDL] PRINT (Print Screen) key event and full screen problems in wind
-- Message: 19392   --  Next: 19393   ----------------------------------------
Then the second problem. Our emulator has a way to set the output window
to 960x720 (3 times 320x240). When setting SDL to full screen, this    
works fine on X11 and with the windib driver. On one of our (Windows    
using) team mate's laptop, he gets a 1400x1040 resolution (with borders)
then. But, when using the windx driver, he gets an error, caused by the
fact that no surface can be created with a SDL_SetVideoMode call... A
similar thing happened on one of our other Windows team member's machine.

Normally, SDL simply does the next-larger resolution with borders, which
indeed worked for the windib driver. But it did not work for the windx
driver! So, why doesn't it work with windx, while it does work with
windib, that resolution, albeit with borders on 1400x1050?

If we modify the code and choose the nearest resolution ourselves
(1024x768), it does work on that same system.
Comment 1 Sam Lantinga 2006-03-14 01:29:26 UTC 
I tried this myself, on my desktop PC, and the DirectDraw driver chose 1024x768 and centered it just fine.

I've sent Manuel e-mail asking if the bug is still active with CVS code.
Comment 2 Ryan C. Gordon 2007-02-12 06:19:59 UTC 
As we're coming up on a year without hearing more on this bug, we'll assume it really was fixed at some point and flag the bug as WORKSFORME.

Please reopen if the bug is still present.

--ryan.