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 4147 - Surfaces not updating correctly
Summary: Surfaces not updating correctly
Status: RESOLVED ABANDONED
Alias: None
Product: SDL
Classification: Unclassified
Component: video (show other bugs)
Version: 2.0.8
Hardware: x86 Windows 10
: P2 major
Assignee: Sam Lantinga
QA Contact: Sam Lantinga
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-04-22 14:59 UTC by anonymatentier
Modified: 2018-08-06 21:20 UTC (History)
0 users

See Also:

Attachments
Shows how the surface/image is before moving, and after moving. (28.65 KB, image/png)
2018-04-22 14:59 UTC, anonymatentier 		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 anonymatentier 2018-04-22 14:59:35 UTC 
Created attachment 3227 [details]
Shows how the surface/image is before moving, and after moving.

Well, it starts simple: I blit an image to the screen, with its coordinates controlled by an SDL_Rect. I compile and run, and it works great. Then, I add an event handler to detect keypresses so I can move the image by changing the coordinates of the SDL_Rect. After being compiled, I run it again. It still seems to work perfectly, and I can move the image just as expected...

But THEN, the surface/image stop updating correctly. Yes, it do continue to move. However, it leaves tracks of the image in the ancient location of the image. In other words, it does not completely erase the precedent image(If you still do not understand, check the photos!)

Oh, yeah: After a while not erasing, it also freezes.

Hope this helps upgrading SDL2.
Comment 1 Ryan C. Gordon 2018-08-06 21:20:20 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.