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 1349 - Fullscreen Alt+Tab under Gnome 3 forces windowed mode, confuses SDL
Summary: Fullscreen Alt+Tab under Gnome 3 forces windowed mode, confuses SDL
Status: RESOLVED ABANDONED
Alias: None
Product: SDL
Classification: Unclassified
Component: video (show other bugs)
Version: HG 2.0
Hardware: x86 Linux
: P2 normal
Assignee: Sam Lantinga
QA Contact: Sam Lantinga
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-20 21:22 UTC by Ellie
Modified: 2018-08-06 21:20 UTC (History)
0 users

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 Ellie 2011-12-20 21:22:18 UTC 
When alt+tab'ing a fullscreen SDL 1.3 OpenGL renderer window, gnome shell apparently forces it into windowed mode. However, SDL never notices it is now windowed.

The result is all sort of weird behavior (e.g. dragging the window will minimize it), and the window will never get fullscreen again by itself.

A possible workaround is doing this for SDL_WINDOWEVENT_FOCUS_GAINED:

SDL_SetWindowFullscreen(window, SDL_FALSE);
SDL_SetWindowFullscreen(window, SDL_TRUE);

Just setting it to SDL_TRUE doesn't work because SDL believes to be fullscreen and ignores it.

That workaround seems ugly to me however, especially for platforms/drivers where SDL wasn't actually windowed and where this might cause a device loss, therefore possibly trashing all textures. (Last time I read about this, Windows seemed to be doing such things for Direct3D)
Comment 1 Ryan C. Gordon 2015-02-19 05:22:16 UTC 
Marking a large number of bugs with the "triage-2.0.4" keyword at once. Sorry if you got a lot of email from this. This is to help me sort through some bugs in regards to a 2.0.4 release. We may or may not fix this bug for 2.0.4, though!
Comment 2 Ryan C. Gordon 2018-08-06 21:20:25 UTC 
Hello, and sorry if you're getting dozens of copies of this message by email.

We are closing out bugs that appear to be abandoned in some form. This can happen for lots of reasons: we couldn't reproduce it, conversation faded out, the bug was noted as fixed in a comment but we forgot to mark it resolved, the report is good but the fix is impractical, we fixed it a long time ago without realizing there was an associated report, etc.

Individually, any of these bugs might have a better resolution (such as WONTFIX or WORKSFORME or INVALID) but we've added a new resolution of ABANDONED to make this easily searchable and make it clear that it's not necessarily unreasonable to revive a given bug report.

So if this bug is still a going concern and you feel it should still be open: please feel free to reopen it! But unless you respond, we'd like to consider these bugs closed, as many of them are several years old and overwhelming our ability to prioritize recent issues.

(please note that hundred of bug reports were sorted through here, so we apologize for any human error. Just reopen the bug in that case!)

Thanks,
--ryan.