-
-
Notifications
You must be signed in to change notification settings - Fork 185
Fix scaled-after-non-scaled usage #2925
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As Anktith said, this works for me with SDL 2.30.2, with the original reproducer.
114ca2d
to
22d5656
Compare
A bit of interesting history: these new API functions were basically added for us by the SDL folks in response to issue #2190 so we have to make use of it! |
22d5656
to
1434bd4
Compare
It doesn't fix #2376 as of now, but SDL has patched the underlying issue and the fix should be available in the next SDL bump, so let this PR wait for that |
1084774
to
61ed0ec
Compare
After the latest rebase, this PR should fix the issue on mac as well. |
Tested on my Mac (reminder it's a 2015 Intel based MacBook Pro) and yes indeed the tests were successful with the latest PR, thanks! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The code addition makes sense to me and the users reported the issue being fixed :)
this PR fixes #2737 and fixes #2376 (they are essentially the same issue).
Note that I couldn't reproduce the original issue on Ubuntu, however @zoldalma999 has tested this branch and reported that this fix has worked on windows. Would be nice if someone gave this a test on a mac as well.
Also worth mentioning that the fix only works for SDL 2.28.0+, but all the wheels we distribute are on 2.30.3 so this shouldn't be a big deal.
It was also mentioned in one of the linked issues that #2571 is also the same issue, but I don't think that's the case.