This bug report was migrated from our old Bugzilla tracker.

These attachments are available in the static archive:

• Test case (test.c, text/plain, 2014-09-09 16:25:46 +0000, 1362 bytes)

Reported in version: 2.0.3
Reported for operating system, platform: Windows 7, x86_64

Comments on the original bug report:

On 2014-09-09 16:25:46 +0000, Andreas Falkenhahn wrote:

Created attachment 1866
Test case

I am experiencing some window refresh trouble. In particular, redrawing the whole shebang on SDL_WINDOWEVENT_EXPOSED does not seem sufficient.

I am attaching a very small example that shows that on Windows 7 and SDL 2.0.3
redrawing on SDL_WINDOWEVENT_EXPOSED is not enough. To reproduce, do the
following:

1. Start the program
2. Maximize the window
3. Minimize the window to the taskbar
4. Unminimize the window from the taskbar again ---> surprisingly, the result is a completely black window although I'm clearly redrawing everything on SDL_WINDOWEVENT_EXPOSED

As SDL_video.h clearly says that

SDL_WINDOWEVENT_EXPOSED,        /**< Window has been exposed and should be
                                     redrawn */

I think that I am not supposed to redraw on any other events but only
on EXPOSED. But as you can see in the small demo source, it doesn't really
work. At least not on Win7 with SDL 2.0.3...

On 2018-08-06 21:20:19 +0000, Ryan C. Gordon wrote:

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.