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 2282 - SDL_GetWindowFlags() returns incorrect flags for maximized windows
Summary: SDL_GetWindowFlags() returns incorrect flags for maximized windows
Status: RESOLVED FIXED
Alias: None
Product: SDL
Classification: Unclassified
Component: video (show other bugs)
Version: 2.0.1
Hardware: x86_64 Windows 7
: P2 normal
Assignee: Sam Lantinga
QA Contact: Sam Lantinga
URL:
Keywords: target-2.0.4
Depends on:
Blocks:
 
Reported: 2013-12-02 20:34 UTC by RetiredSphinx
Modified: 2015-05-28 19:24 UTC (History)
0 users

See Also:

Attachments
A small program that demonstrates the problem. It creates a window, maximizes it, waits one second, and prints the output of SDL_GetWindowFlags() and IsZomed() (1.08 KB, text/x-c++src)
2013-12-02 20:34 UTC, RetiredSphinx 		Details
View All 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 RetiredSphinx 2013-12-02 20:34:41 UTC 
Created attachment 1481 [details]
A small program that demonstrates the problem. It creates a window, maximizes it, waits one second, and prints the output of SDL_GetWindowFlags() and IsZomed()

SDL_GetWindowFlags() never returns SDL_WINDOW_MAXIMIZED, even when the window is indeed maximized, either by SDL or by the Windows graphical interface.

My simple example program creates a window, maximizes it, shows the window for one second to demonstrate that it is indeed maximized, and outputs the result of SDL_GetWindowFlags() AND'ed with SDL_WINDOW_MAXIMIZED. The output is always 0 on my system, while the Win32 call on the base HWND immediately following always outputs 1.
Comment 1 Ryan C. Gordon 2015-02-19 05:22:19 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 2015-04-07 04:57:58 UTC 
(sorry if you get a lot of copies of this email, I'm marking several bugs at once)

Marking bugs for the (mostly) final 2.0.4 TODO list. This means we're hoping to resolve this bug before 2.0.4 ships if possible. In a perfect world, the open bug count with the target-2.0.4 keyword is zero when we ship.

(Note that closing a bug report as WONTFIX, INVALID or WORKSFORME might still happen.)

--ryan.
Comment 3 Sam Lantinga 2015-05-28 19:24:32 UTC 
This is fixed in 2.0.4, thanks!