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 2112

Summary: With SDL_WINDOW_RESIZABLE, drawing textures with Alpha no longer works once you've changed the size of the window.
Product: SDL Reporter: solar.strings
Component: renderAssignee: Sam Lantinga <slouken>
Status: RESOLVED ABANDONED QA Contact: Sam Lantinga <slouken>
Severity: normal    
Priority: P2    
Version: 2.0.0   
Hardware: x86_64   
OS: Windows 7   

Description solar.strings 2013-09-24 04:13:43 UTC 
I wanted to try out the SDL_RenderSetScale() function, and thought it would be neat to have the graphics scaled to whatever window size the user prefers. However, as soon as I drag one of the corners of the window, all textures are drawed with full opacity, and setting the Alpha on a texture afterwards, doesn't work.

Order:
1. Set SDL_WINDOW_RESIZABLE flag when calling SDL_CreateWindow
2. Draw any texture with alpha set below 255 (preferably something you can see is transparent like 128)
3. Looks fine
4. Resize the window
5. The texture will be drawed witout the Alpha (Opacity = 100%)
6. Try to set the Alpha of the texture to a transparent value
7. Nothing happens, the texture is still drawed with 100% Opacity

Video:
http://www.youtube.com/watch?v=616q-6Bswaw
Comment 1 Sam Lantinga 2013-09-28 06:11:05 UTC 
I believe this is fixed in the latest snapshot.  Can you confirm?
http://www.libsdl.org/tmp/SDL-2.0.zip
Comment 2 solar.strings 2013-09-29 04:23:27 UTC 
Compiled the latest snapshot: SDL-2.0.0-7750, and tried,still the same result.
Comment 3 solar.strings 2013-10-09 13:04:21 UTC 
After adding some more textures to test with, I also found that the texture's edges get artifacts as well when the window is resized.

This was tested with SDL versions: 2.0.0 and 2.0.0-7791 

Video:
http://www.youtube.com/watch?v=_gWV2DaRyDw
Comment 4 Ryan C. Gordon 2018-08-06 21:20:23 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.