Repository navigation
dpi= doesn't seem to have any effect with MacOS X backend #113
Description
I am using the MacOS X backend, and when plotting and saving a file, the dpi= option seems to be ignored:
fig = plt.figure()
ax = fig.add_subplot(1,1,1)
fig.savefig('test.tif', dpi=1000)
produces a file that has dpi=72. Is this normal, or is it a bug? If it is normal that dpi doesn't have any effect, it might be worth adding a warning so the user knowns the dpi option will be ignored.
Activity
mdboom commented on Jun 15, 2011
I don't think Michiel de Hoon, the Mac OS X backend developer, has come over to github yet. This is a good bug for him to track down. I'm milestoning it pretty far off since it's not a blocker.
mdboom commented on Aug 20, 2012
@pelson: If Michiel can't be reached, do you want to tackle this since you're on OS-X?
pelson commented on Aug 20, 2012
:-) I had a look about a month ago and it wasn't immediately obvious. Were you thinking for the 1.2 release? I'm not likely to get a good look at this for around 9 days, which might be acceptable if it is a simple bug fix I suppose. What do you think?
mdboom commented on Aug 20, 2012
That's fine. No need to do this now -- if it gets in by the release candidate that would be great, but this is not a top burning issue either.
dmcdougall commented on Sep 7, 2012
Having looked at the macosx backend code for the past few days, I know exactly why this is happening. The dpi is never even passed to the graphics context, so it uses some kind of default, probably 72 dpi.
dmcdougall commented on Oct 1, 2012
Closing; #1230 fixes this.
Merge pull request matplotlib#113 from hyperspy/bug_in_stack