matplotlib-devel Mailing List for matplotlib

Hello,
I found what I believe is bug in matplotlib.
The program
 from matplotlib.matlab import *
 from math import sin
 t=3Darange(0,10,0.1)
 x=3Dmap(lambda tt:sin(tt), t)
 figure(figsize=3D(5,3))
 plot(t,x,"k-")
 xlabel("total time")
 ylabel("tatil tome")
 title("titol tame")
 show ()
displays a graph, where the xlabel is shifted to much down. Only the
upper half of the xlabel is still visible, the lower half is outside
the visible area.
Is this a bug? Or do I need to somehow manually reserve space for the
display of the xlabel?
All the best,
Jochen
--=20
http://seehuhn.de/

Hello,
I fixed the problem with the not-quite-correctly text in the PS
backend. The solution was to shift all the text up by the distance
between the lower edge of the bounding box and the text base line. I
added a new method to FT2Font, which calculates this distance.
Comments about this are most welcome.
All the best,
Jochen
--=20
http://seehuhn.de/

Hello,
I did some clean-up of the matplotlib PostScript backend.
Main changes:
 - The generated Postscript output is now completely DSC conformant
 (I hope).
 - All PostScript definitions go into a a PostScript dictionary
 mpldict instead of the global one. This will hopefully prevent
 problems (name clashes) when including matplotlib generated eps
 files into other PostScript files
 - I moved 1.5kb of comments about drawing ellipses from the generated
 PostScript into a Python source code comment. I think it does not
 make sense to ship the comment in each and every genereated picture.
Hopefully I did not cause any new problems. Comments about the
changes are most welcome.
All the best,
Jochen
--=20
http://seehuhn.de/

Hello,
currently I am having a closer look at the PostScript backend.
Some questions occurred to me:
1) What is the meaning of 'backend_version'? When should it
 be increased/changed?
2) Is the following code the correct way to get the
 matplotlib version for use in a backend file:
 from matplotlib import __version__
 version=3D__version__
3) The draw_lines method checks whether the argument arrays
 are of the same size as required. The other functions do not
 do any sanity checks on the arguments. Can the renderer methods
 assume that they are called with semantically correct arguments?
 Is it ok to fail with an Python exception otherwise?
4) Can the PostScript code assume that each file contains only one
 picture/page? Might this change in the future?
5) Does matplotlib have the concept of a picture title which could
 be written into the DSC "%%Title" comment? If the answer is yes:
 how do I get this title?
Also I have some questions about the template backend in
backend_template.py:
6) The template backend contains the line
 from matplotlib.transforms import Bbox
 Does this have any function or should it be removed?
7) The template backend uses=20
 verbose.report('Error: %s'%msg)
 Should this be 'verbose.report_error' instead?
Sorry about having so many questions,
Jochen
--=20
http://seehuhn.de/

John,
I think the doc string for points_to_pixels() in backend_bases.py and
backend_template.py should be updated define its return type.
Does points_to_pixels() return int, float, or float if the backend
supports it (agg) else int (gtk)?
Regards
Steve