matplotlib-users Mailing List for matplotlib

On 20/09/06, John Hunter <jdh...@ac...> wrote:
> >>>>> "George" == George Nurser <gn...@go...> writes:
>
>     George> SVN revision 2774, linux 64-bit, TkAgg, NumPy.  If I
>     George> create a figure on the screen (TkAgg back end), when I try
>     George> to save it as .ps, the resulting file displays and prints
>     George> as blank.  However I can save it as .eps (or png)
>     George> perfectly well.
>
> tkagg passes its printing off to agg, which passes both *.ps and *.eps
> to backend_ps with no further processing.  So if there is a problem,
> it should show up on a pure PS backend, eg
>
> import matplotlib
> matplotlib.use('PS')
> from pylab import figure, show
> fig = figure()
> ax = fig.add_subplot(111)
> ax.plot([1,2,3])
> fig.savefig('test.ps')
> fig.savefig('test.eps')

>
> Is anyone seeing problems with this?


John,
I tried this and, again, the ps fails but eps is OK.

>
> There is, however, a known bug when using tkagg from pylab, after you
> click the save button pylab loses the current figure.  This appears to
> be a tkinter bug and I reported it on python-list and go no response.
> If this is the cause of your problem, it is not about PS vs EPS vs
> PNG, but about which filetype you try and save first.  The first one
> would work, and subsequent ones would fail.

This certainly wasn't the problem. Originally I tried saving png first
(OK),  ps (not OK),
eps (third time lucky, OK.)

Thanks for responding so quickly. George.

I applied the parts of the patch that don't affect the swig files.
Seems to be working well.

Thanks,
    Charlie

On 9/20/06, Andrew Jaffe <a.h...@gm...> wrote:
> Hi all,
>
> As discussed by David Cooke, above, I think there are still some other
> issues, at least under OSX: several files need to be patch to convert
> int to the new Py_ssize_t, at least in cxx_extensions.cxx and _image.cpp
>
> Will these be changed?
>
> Andrew
>
>
>
> Achim Gaedke wrote:
> > Hi there!
> >
> > I built numpy-1.0b5 and pygtk with python2.5 on Sunday. It worked, but I
> > use numarray as standard numerix extension.
> > There was a bugfix for numpy-1.0b5 that is already contained in their
> > repository version.
> >
> > Yours, Achim
> >
> > Charlie Moad wrote:
> >> It builds now.  We still have to wait on a useable numpy for python2.5
> >> and pygtk for windows/py2.5.  All the other components are there or we
> >> can build.
> >
>
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys -- and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>