Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork7.9k
FIX: Make sure a renderer gets attached to figure after draw#21758
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
Make sure that a cached renderer gets added to the figure aftercalling fig.canvas.draw()
This is legacy from when the OSX backend was not Agg based, but was implemented on top of the OSX native drawing API. In that API we could only get a graphics context inside of the UI draw loop, hence wehad to use |
… to figure after draw
…758-on-v3.5.xBackport PR#21758 on branch v3.5.x (FIX: Make sure a renderer gets attached to figure after draw)
Uh oh!
There was an error while loading.Please reload this page.
PR Summary
Make sure that a cached renderer gets added to the figure after calling fig.canvas.draw() on the macosx backend. This changes the draw path to go through adding a renderer to the figure first.
closes#19197
closes#13968
closes#7550
PR Checklist
Tests and Styling
pytest
passes).flake8-docstrings
and runflake8 --docstring-convention=all
).Documentation
doc/users/next_whats_new/
(follow instructions in README.rst there).doc/api/next_api_changes/
(follow instructions in README.rst there).