8000 Update to Bounding Box for Qt5 FigureCanvasATAgg.paintEvent() by pshriwise · Pull Request #14310 · matplotlib/matplotlib · GitHub
[go: up one dir, main page]

Skip to content

Update to Bounding Box for Qt5 FigureCanvasATAgg.paintEvent() #14310

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

Closed
wants to merge 1 commit into from

Conversation

pshriwise
Copy link
Contributor

PR Summary

This PR is intended to address #14160 by using dimensions of the renderer rather than the QPaintEvent rectangle passed to the paintEvent method. It seems the dimensions of this rectangle are dependent on the event type triggering the paintEvent call (at least in OSX) when using PySide2.

@tacaswell
Copy link
Member

Interesting. That this only happens on OSX + pyside2 suggests that this is an upstream bug. Do we want to gate this based on that?

I think this has the cost that we will no longer do partial redraws?

The documentation was a bit unclear what coordinate system the rectangle on the event is in....

@tacaswell tacaswell modified the milestones: v3.1.1, v3.2.0 May 26, 2019
@pshriwise
Copy link
Contributor Author

@tacaswell Yeah I took a look at that too and it wasn't clear what would be passed in for all situations.

It might be possible to distinguish between a QPaintEvent coming from a window resize and a drag/scroll higher up in the call stack, but I'm not sure.

I'm not sure if this same behavior is true for PyQT5 or not. It might be.

Should I go ahead and upgrade this to true PR?

@pshriwise
Copy link
Contributor Author

Closing this PR in favor of #14456.

@pshriwise pshriwise closed this Jun 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants
0