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

Fix incorrect behaviour from BitmapClip when fps != 1 #1333

Merged
merged 2 commits into from
Oct 6, 2020

Conversation

tburrows13
Copy link
Collaborator

Closes #1326.
Added tests 1 and 3 fail without this PR. Test 1 (fps < 1) would crash and test 3 (fps > 1) would return the wrong results.

  • I have provided code that clearly demonstrates the bug and that only works correctly when applying this fix
  • I have added suitable tests demonstrating a fixed bug or new/changed feature to the test suite in tests/
  • I have formatted my code using black -t py36

@tburrows13 tburrows13 added the bug-fix For PRs and issues solving bugs. label Oct 6, 2020
@coveralls
Copy link

coveralls commented Oct 6, 2020

Coverage Status

Coverage increased (+0.3%) to 67.861% when pulling 114a0ff on tburrows13:fix-BitmapClip into 0e4bf6d on Zulko:master.

@tburrows13 tburrows13 merged commit 873530e into Zulko:master Oct 6, 2020
@tburrows13 tburrows13 deleted the fix-BitmapClip branch October 6, 2020 14:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug-fix For PRs and issues solving bugs.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

BitmapClip produces wrong output with fps != 1
2 participants