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 2642 - SDL_WINDOW_FULLSCREEN_DESKTOP window disappears with SDL_PumpEvents
Summary: SDL_WINDOW_FULLSCREEN_DESKTOP window disappears with SDL_PumpEvents
Status: RESOLVED ABANDONED
Alias: None
Product: SDL
Classification: Unclassified
Component: video (show other bugs)
Version: 2.0.3
Hardware: x86_64 Linux
: P2 normal
Assignee: Ryan C. Gordon
QA Contact: Sam Lantinga
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-07-14 21:13 UTC by Ben Boeckel
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 Ben Boeckel 2014-07-14 21:13:03 UTC 
In the process of debugging why fullscreen support isn't working in one of my apps[1], it looks like I'm getting a bunch of events that I shouldn't be in full screen which don't happen in windowed mode. The code which sets up the window is here[2]. Am I setting it up wrong or should I really be getting MINIMIZED events?

By putting sleep() in between calls, I was able to track it down to the SDL_PollEvent[3] call and further poking showed that calling SDL_PumpEvents triggers the disappearance of the window. Is SDL doing something wrong with the events that get sent by X in the fullscreen case?

FWIW, I'm using XMonad, so maybe this is related to Bug #985. I'll try it out with a more standard WM later this week.

[1]https://github.com/mathstuf/abagames-gunroar/issues/1
[2]https://github.com/mathstuf/abagames-gunroar/blob/master/src/abagames/util/sdl/screen3d.d#L48
[3]https://github.com/mathstuf/abagames-gunroar/blob/master/src/abagames/util/sdl/screen3d.d#L48
Comment 1 Ryan C. Gordon 2018-08-06 21:20:24 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.