Skip to content

BUG: OSX backend, Figure.set_dpi() gets confused on retina display #6501

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
efiring opened this issue May 30, 2016 · 2 comments
Closed

BUG: OSX backend, Figure.set_dpi() gets confused on retina display #6501

efiring opened this issue May 30, 2016 · 2 comments

Comments

@efiring
Copy link
Member

efiring commented May 30, 2016

On v2.x, with ipython --pylab=osx:

plot([1,2,3])
gcf().set_dpi(115)

It now displays the result with an image size based on true dpi rather than pixel-doubled dpi used originally. Subsequent attempts to change dpi result in nothing being plotted.

@efiring efiring added this to the 2.0.1 (next bug fix release) milestone May 30, 2016
@jenshnielsen
Copy link
Member

Somewhat related if an OSX backend figure is dragged from a hidpi screen to a low dpi screen or the other way the figure is blanked (the toolbar buttons stays and are even correctly repainted in the right resolution)

@QuLogic QuLogic modified the milestones: 2.0.1 (next bug fix release), 2.0.2 (next bug fix release) May 3, 2017
@tacaswell tacaswell modified the milestones: 2.1.1 (next bug fix release), 2.2 (next feature release) Oct 9, 2017
@greglucas
Copy link
Contributor

The macosx dpi scaling issues were sorted out in #21365 and this seems to work as expected on my local retina display now.

@story645 story645 removed this from the future releases milestone Oct 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants