Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Surfaces not updating correctly #2880

Closed
SDLBugzilla opened this issue Feb 11, 2021 · 0 comments
Closed

Surfaces not updating correctly #2880

SDLBugzilla opened this issue Feb 11, 2021 · 0 comments
Labels
abandoned Bug has been abandoned for various reasons

Comments

@SDLBugzilla
Copy link
Collaborator

This bug report was migrated from our old Bugzilla tracker.

These attachments are available in the static archive:

Reported in version: 2.0.8
Reported for operating system, platform: Windows 10, x86

Comments on the original bug report:

On 2018-04-22 14:59:35 +0000, wrote:

Created attachment 3227
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.

On 2018-08-06 21:20:20 +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.

@SDLBugzilla SDLBugzilla added abandoned Bug has been abandoned for various reasons bug labels Feb 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
abandoned Bug has been abandoned for various reasons
Projects
None yet
Development

No branches or pull requests

1 participant