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 3213

Summary: SDL_Renderer stops rendering, with app on-screen, via special sequence of window operations
Product: SDL Reporter: David Ludwig <dll>
Component: videoAssignee: Sam Lantinga <slouken>
Status: RESOLVED DUPLICATE QA Contact: Sam Lantinga <slouken>
Severity: major    
Priority: P2 CC: dll, philipp.wiesemann
Version: 2.0.3   
Hardware: x86   
OS: Windows (All)   
Attachments: Win32-based bug demo-app

Description David Ludwig 2015-12-24 10:29:27 UTC 
On Windows platforms, *both* Win32 and WinRT, SDL_Renderer calls can fail to do anything, provided that a special sequence of windowing operations are undertaken.

To note, this bug was reproduced via MSVC 2015 running on Windows 10.  It may happen elsewhere, I'm not sure though.

Steps to Reproduce:
1. create an SDL_Renderer-capable Windows app, one with a resizable, non-fullscreen window.  (Sample app + code + project is forthcoming.)
2. launch app
3. maximize window via app-window's maximize button
4. minimize window via app-window's minimize button
5. alt-tab back to app-window

Expected Results:
App-window restores, and continues to render new content

Observed Results:
App-window restores, but rendering no longer works, and new content is no longer drawn.

Additional Notes:
* Via stepping through the code, it appears that many SDL_Renderer calls fail to work (after the Steps to Reproduce have been employed), as the renderer's "hidden" property is set to SDL_TRUE.
Comment 1 David Ludwig 2015-12-24 11:20:10 UTC 
Confirmed -- this bug occurs in SDL 2.0.3, in Win32 apps
Comment 2 David Ludwig 2015-12-24 11:23:20 UTC 
Created attachment 2345 [details]
Win32-based bug demo-app

This demo includes source, and pre-built binaries, with which to view this bug.
Comment 3 Philipp Wiesemann 2015-12-25 12:28:12 UTC 
Maybe related to bug 3202.
Comment 4 David Ludwig 2015-12-27 18:04:58 UTC 
Yup, this looks like a duplicate.

Thanks, Philipp!

*** This bug has been marked as a duplicate of bug 3202 ***