GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — dpi= doesn't seem to have any effect with MacOS X backend · Issue #113 · matplotlib/matplotlib

dpi= doesn't seem to have any effect with MacOS X backend #113

New issue
Copy link
New issue
Copy link
Closed
Closed
dpi= doesn't seem to have any effect with MacOS X backend#113
Copy link
Labels
status: confirmed bug
Milestone
v1.2.x

Description

@astrofrog
astrofrog
opened on May 11, 2011
Issue body actions

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

  1. mdboom commented on Jun 15, 2011

    @mdboom
    mdboom
    on Jun 15, 2011
    Member
    More actions

    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.

  2. mdboom commented on Aug 20, 2012

    @mdboom
    mdboom
    on Aug 20, 2012
    Member
    More actions

    @pelson: If Michiel can't be reached, do you want to tackle this since you're on OS-X?

  3. pelson commented on Aug 20, 2012

    @pelson
    pelson
    on Aug 20, 2012
    Member
    More actions

    :-) 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?

  4. mdboom commented on Aug 20, 2012

    @mdboom
    mdboom
    on Aug 20, 2012
    Member
    More actions

    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.

  5. dmcdougall commented on Sep 7, 2012

    @dmcdougall
    dmcdougall
    on Sep 7, 2012
    Member
    More actions

    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.

  6. dmcdougall commented on Oct 1, 2012

    @dmcdougall
    dmcdougall
    on Oct 1, 2012
    Member
    More actions

    Closing; #1230 fixes this.

  7. dmcdougall
    closed this as completedon Oct 1, 2012
  8. magnunor
    added a commit that references this issue on Dec 5, 2013

    Merge pull request matplotlib#113 from hyperspy/bug_in_stack

    d88c734
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    status: confirmed bug

    Type

    No type

    Projects

    No projects

      Milestone

      • v1.2.x

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      You are visitor 01402503 — GeezerVison does not store the pages you look up.
      Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.