Skip to content

Avoid double draw in qt5cairo. #10399

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Feb 11, 2018
Merged

Avoid double draw in qt5cairo. #10399

merged 1 commit into from
Feb 11, 2018

Conversation

anntzer
Copy link
Contributor

@anntzer anntzer commented Feb 8, 2018

PR Summary

Fix the double draw mentioned in #10210 (comment). Better solution is likely to move this to the backend_cairo base class (as done by mplcairo) but that's a bit more surgery, for the next time...

PR Checklist

  • Has Pytest style unit tests
  • Code is PEP 8 compliant
  • New features are documented, with examples if plot related
  • Documentation is sphinx and numpydoc compliant
  • Added an entry to doc/users/next_whats_new/ if major new feature (follow instructions in README.rst there)
  • Documented in doc/api/api_changes.rst if API changed in a backward-incompatible way

@tacaswell tacaswell added this to the v2.2 milestone Feb 11, 2018
@tacaswell tacaswell merged commit a409c01 into matplotlib:master Feb 11, 2018
@anntzer anntzer deleted the qt5cairo-doubledraw branch February 11, 2018 10:26
@QuLogic QuLogic modified the milestones: needs sorting, v2.2.0 Feb 12, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
backend: cairo GUI: Qt
Projects
None yet
Milestone
v2.2.0
Development

Successfully merging this pull request may close these issues.
3 participants
@anntzer @tacaswell @QuLogic