matplotlib-users Mailing List for matplotlib

>>>>> "matthew" == matthew arnison <ma...@ca...> writes:

    matthew> * when saving from the GTK window into a .ps file, the
    matthew> lines are not clipped by the edge of the plot area: see
    matthew> the top left plot in the attached code

I've made a number of changes to matplotlib to improve the PS
functionality -- those of you who are interested should take this
version for a test drive and let me know of any problems so I can fix
them for the next release.

  http://nitace.bsd.uchicago.edu:8080/files/share/matplotlib-0.42g.tar.gz

Note WX is not working (but will be soon) with this snapshot so wx
users please do not download.

Added:

  * I think I've fixed all the backend switching problems, you can now
    output PS from the GTK backend by adding the PS extension.  This
    will be available in WX soon.  Let me know if you find any
    lingering bugs.

 * EPS (at long last!).  Just use an 'eps' extension and the bounding
   box will be added to the PS output.  


    matthew> * xaxis and yaxis labels often land on top of adjacent
    matthew> subplot titles and plot areas in savefig('blah.ps')
    matthew> output (I've had trouble with this in the -dPS output
    matthew> too)

Yep, axes don't communicate with one another for text layout.  A few
things which you can do to help

 1) Turn off redundant x labels.  If 2 subplots use the same x axis,
    turn off the tick labels in all but the lower one with 

    set(gca(), 'xticklabels', [])

 2) Make the tick labels and titles smaller

    t = get(gca(), 'xticklabels')
    set(t, 'fontsize', 8)

    t = title('my title')
    set(t, 'fontsize', 10)

 3) control the placement of the title manually

    t = title('my title')
    t.set_y(0.95)

    1.0 is the top of the y axis.  1.02 is the default.  Numbers less
    than 1 will be below the y axis.  Eg, to make the title top
    aligned and below the top of the y axis, do

    t = title('my title', verticalalignment='top')
    t.set_y(0.99)

I'm open to suggestions for changing the defaults (eg making the
default fonts smaller) if people are having these kinds of problems
regularly.

JDH    

>>>>> "John" == John Hunter <jdh...@ac...> writes:
    Kuzminski> #2 above is the answer to the problem in my original
    Kuzminski> post. However I have another question.  When I set the
    Kuzminski> ylabel rotation to be horizontal, the beginning of the
    Kuzminski> text is truncated ( the width of the border does not
    Kuzminski> compensate ).  I'm happy to set it wider but am
    Kuzminski> wondering how ( what controls the width of the area
    Kuzminski> where the labels gets written ).  

In this case the placement of the ylabel is determined by the
horizontalalignment and the left side of the y tick labels.  If it is
being truncated, you have a few choices.

  1) Use a different alignment or smaller fontsize for the label

  2) Use a smaller font size for the y tick labels or turn them off
     entirely -- the position of the ylabel will automatically adjust
     based upon the size of the tick labels.

  3) Probably best, make a custom axes where the 'left' parameter is
     larger and the width parameter is smaller.  This will give you
     more room for your ylabel.

    Kuzminski> I also noticed that title of the graph ( with the
    Kuzminski> horizontal alignment set to bottom ) is too close to
    Kuzminski> the top of the graph itself, is there a way to pad
    Kuzminski> that?

When you set the title, do

   t = title('my title')
   t.set_y(1.05)  # relative axes coords

1.0 is the top of the axes, so the larger the number the higher the
title will be.  1.02 is the default.

Hope this helps,
JDH

>>>>> "Kuzminski," == Kuzminski, Stefan R <SKu...@fa...> writes:

    Kuzminski> I attached a '_gd.dll'.  This is the C python
    Kuzminski> extension that the gd.py module from gdmodule imports.
    Kuzminski> It goes directly in site-packages.  I built it
    Kuzminski> statically linked to zlib, libpng, freetype and the gd
    Kuzminski> lib.  I don't have the time at the moment to fuss with
    Kuzminski> getting it to use the dlls.  ( or to add the jpeg
    Kuzminski> support ) The precompiled windows GD dll in particular
    Kuzminski> seems to not export a few functions that gdmodule
    Kuzminski> wants which is a real pain.

Excellent, the easier the better...


    Kuzminski> 2) This one took me a long time to figure out.  For
    Kuzminski> some reason opening a windows file in Python with 'wb'
    Kuzminski> permission will cause the png files to be corrupted
    Kuzminski> above a certain image size.  If you pass the filename
    Kuzminski> to gdmodule, then the gdmodule opens the file and it
    Kuzminski> works.  I imagine that the python call "open(
    Kuzminski> 'filename', 'wb' )" just calls fopen, furthermore I
    Kuzminski> thought that binary mode only applied to reading
    Kuzminski> files.  At any rate, I have no idea why this doesn't
    Kuzminski> work in this case but it doesn't.  To get it to work,
    Kuzminski> I had to change line 261 in backends_gd.py to pass the
    Kuzminski> filename rather than a file object, this is the only
    Kuzminski> modification to Matplotlib I had to make.

Could be that I don't have the text bounding boxes exactly right in
gdmodule.  In axes.py there is a line on or around line 454

if 0:

if you replace that with 

if 1:

the text bounding boxes will be displayed.  If they are not exactly
right, then the text layout will also be off.  I'll take a look when I
get some time, but in the mean time you may want to see for yourself.

Re: gdmodule on windows.  What did you do for fonttools?  Did you also
build this yourself?  If I recall correctly I built it once on windows
without too much difficulty (back when I was trying to get gd working
on windows) but it's been a while and I didn't keep notes.  I didn't
see an installer on the sf site.

JDH


    Kuzminski>         im.writePng( filename )



    Kuzminski> #2 above is the answer to the problem in my original
    Kuzminski> post. However I have another question.  When I set the
    Kuzminski> ylabel rotation to be horizontal, the beginning of the
    Kuzminski> text is truncated ( the width of the border does not
    Kuzminski> compensate ).  I'm happy to set it wider but am
    Kuzminski> wondering how ( what controls the width of the area
    Kuzminski> where the labels gets written ).  I also noticed that
    Kuzminski> title of the graph ( with the horizontal alignment set
    Kuzminski> to bottom ) is too close to the top of the graph
    Kuzminski> itself, is there a way to pad that?

    Kuzminski> thanks, Stefan

    Kuzminski> -----Original Message----- From: John Hunter
    Kuzminski> [mailto:jdh...@ni...] Sent:
    Kuzminski> Friday, January 23, 2004 6:58 AM To: Kuzminski, Stefan
    Kuzminski> R Cc: mat...@li... Subject:
    Kuzminski> Re: [Matplotlib-users] broken PNG files with GD
    Kuzminski> backend

>>>>> "Kuzminski," == Kuzminski, Stefan R <SKu...@fa...>
    Kuzminski> writes:

    Kuzminski> Now on to my specific problem.  I'm using the GD
    Kuzminski> backend on Windows with Matplotlib 0.41.

    Kuzminski> First things first -- I haven't succeeded in getting
    Kuzminski> the gd backend compiled on windows.  If you have some
    Kuzminski> expertise here and are willing to share, or better yet
    Kuzminski> build a gdmodule and gd installer that I can put on
    Kuzminski> the website, I would be very much obliged!  I
    Kuzminski> contacted the gdmodule maintainer some time ago over
    Kuzminski> this issue and he had never built it on windows
    Kuzminski> either.  In my googling, I discovered the perl gd
    Kuzminski> module for windows and following their lead, succeeded
    Kuzminski> in building gd lib, but ran into some troubles (can't
    Kuzminski> remember what) building gdmodule.

    Kuzminski> If I set the dpi to over 60 the png file that gets
    Kuzminski> generated is 'empty', it's only 17 bytes long.  As soon
    Kuzminski> as I drop he DPI to below 65 or so, I get the image
    Kuzminski> file correctly.  This is with the simple_plot.py
    Kuzminski> example.

    Kuzminski> Now on to your problem. Is there a typo here?  You say
    Kuzminski> over 60 is empty and under 65 is ok ??  Can you send
    Kuzminski> me a script which replicates the problem, with the two
    Kuzminski> calls to savefig, one which has the problem and which
    Kuzminski> does not.  Then I can begin to diagnose the problem;
    Kuzminski> see if it occurs under linux, see if it's a gd
    Kuzminski> problem, see if it's a problem on my end, etc....

    Kuzminski> Are you using matplotlib + GD for a web app server?

    Kuzminski> John Hunter