Thanks to visit codestin.com
Credit goes to github.com

Skip to content

DPI in pdf (other MixedModeBackends?) not properly reported during draw. #9220

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
jklymak opened this issue Sep 24, 2017 · 2 comments
Closed
Assignees
Labels
backend: pdf status: closed as inactive Issues closed by the "Stale" Github Action. Please comment on any you think should still be open. status: inactive Marked by the “Stale” Github Action

Comments

@jklymak
Copy link
Member

jklymak commented Sep 24, 2017

Bug report

This is a catchall for various PDF positioning issues.

#9204
#8120
#9082
#6827
#6227
#3918 (maybe fixed?)
#15497
#16641

I'll document w/ tests ASAP.

Code for reproduction

# Paste your code here
#
#

Actual outcome

# If applicable, paste the console output here
#
#

Expected outcome

Matplotlib version

  • Operating System:
  • Matplotlib Version:
  • Python Version:
  • Jupyter Version (if applicable):
  • Other Libraries:
@jklymak jklymak self-assigned this Sep 24, 2017
@jklymak
Copy link
Member Author

jklymak commented Sep 25, 2017

Also constrained_layout behaves funny. If I print a PDF first any pngs printed subsequently are broken.

Ahem, only if done using the notebookAgg!. Works fine from Qt5Agg

Breaks if I use pdf backend as well.

@tacaswell tacaswell added this to the 2.2 (next next feature release) milestone Sep 26, 2017
@github-actions
Copy link

This issue has been marked "inactive" because it has been 365 days since the last comment. If this issue is still present in recent Matplotlib releases, or the feature request is still wanted, please leave a comment and this label will be removed. If there are no updates in another 30 days, this issue will be automatically closed, but you are free to re-open or create a new issue if needed. We value issue reports, and this procedure is meant to help us resurface and prioritize issues that have not been addressed yet, not make them disappear. Thanks for your help!

@github-actions github-actions bot added the status: inactive Marked by the “Stale” Github Action label Apr 18, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 18, 2023
@rcomer rcomer added the status: closed as inactive Issues closed by the "Stale" Github Action. Please comment on any you think should still be open. label May 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend: pdf status: closed as inactive Issues closed by the "Stale" Github Action. Please comment on any you think should still be open. status: inactive Marked by the “Stale” Github Action
Projects
None yet
Development

No branches or pull requests

3 participants