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 2637 - Entering fullscreen with the "Spaces" button on OSX does not update SDL_GetWindowFlags()
Summary: Entering fullscreen with the "Spaces" button on OSX does not update SDL_GetWi...
Status: RESOLVED INVALID
Alias: None
Product: SDL
Classification: Unclassified
Component: video (show other bugs)
Version: 2.0.3
Hardware: x86 Mac OS X 10.8
: P2 normal
Assignee: Sam Lantinga
QA Contact: Sam Lantinga
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-07-11 11:17 UTC by Daniel Ratcliffe
Modified: 2014-07-12 03:32 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel Ratcliffe 2014-07-11 11:17:19 UTC
When running on OSX 10.8 or above with SDL_HINT_VIDEO_MAC_FULLSCREEN_SPACES set to 1 (the default), using the button on the window UI to enter or leave fullscreen mode does not set or clear any window flags. I would expect SDL.SDL_GetWindowFlags to contain either SDL_WINDOW_FULLSCREEN or SDL_WINDOW_FULLSCREEN_DESKTOP after entering fullscreen, and to contain neither after leaving fullscreen. Currently the flags do not change, staying at their intial values or whatever they were most recently set to by  SDL_SetWindowFullscreen.
Comment 1 Alex Szpakowski 2014-07-11 17:37:27 UTC
This is intentional (and good behaviour in my opinion) - see the commit message here: https://hg.libsdl.org/SDL/rev/a2910aa6c056

Keep in mind that the user pressing the button to make the window go into its own Space does not have the same behaviour as the program calling SDL_SetWindowFullscreen(..., SDL_WINDOW_FULLSCREEN_DESKTOP), because the menubar and dock are not fully hidden in the former case. The SDL program can 'enter' fullscreen-desktop mode programmatically at any time, even after the user has pressed that button.
Comment 2 Sam Lantinga 2014-07-12 03:32:12 UTC
Design is clarified.