It seems this stopped working after commit r8906 (svn) or
32f64b01c98d1e3b51be57ab49c899cf91017817:
r8906 | efiring | 2011-01-11 21:53:37 -1000 (Tue, 11 Jan 2011) | 2 lines
Fix eps distillation bbox bug; closes 3032385
I have opened a ticket on GitHub:
https://github.com/matplotlib/matplotlib/
Hello,
It seems that at some point in the last few months a change was made that means
that the following code no longer works properly:
---
import matplotlib as mpl
mpl.use('Agg')
import matplotlib.pyplot as plt
import numpy as np
mpl.rc('text', usetex=True)
fig = plt.figure()
ax = fig.add_a
Willi Richert writes:
>> > Isn't there a convenient way just to not plot the big white rectangle in
>> > matplotlib?
>>
>> It seems that
>>
>> fig=plt.figure(frameon=False)
>>
>> omits the rectangle.
>
> in my version 0.98.5 frameon=False (as a subplot argument) just omits the
> black lines at
As Jouni suggested, the frameon argument needs to be applied to the
figure, not to the axes (or subplot).
Regards,
-JJ
On Mon, Jan 26, 2009 at 10:54 AM, Willi Richert wrote:
> Hi,
>
> in my version 0.98.5 frameon=False (as a subplot argument) just omits the
> black lines at the x and y axes. T
Hi,
in my version 0.98.5 frameon=False (as a subplot argument) just omits the
black lines at the x and y axes. The huge white rectangle is still plotted.
wr
Am Montag, 26. Januar 2009 16:20:10 schrieb Jouni K. Seppänen:
> Willi Richert writes:
> > Isn't there a convenient way just to not plot
Willi Richert writes:
> Isn't there a convenient way just to not plot the big white rectangle in
> matplotlib?
It seems that
fig=plt.figure(frameon=False)
omits the rectangle.
--
Jouni K. Seppänen
http://www.iki.fi/jks
---
Hi,
lots of user requests mentioned the problem of a too big bounding box in saved
figures. Some even provided patches to the svn (http://www.nabble.com/savefig-
with-tight-bounding-box.-td21515002.html).
To date there is no way of automatically getting a figure plotted so tightly
that it could
If you can find a way to create a minimal script, that would be better,
because then we can verify the fix.
But barring anything else, seeing the .eps might help.
Cheers,
Mike
Michael Hearne wrote:
> John - Thanks for the quick fix. I'm having a separate issue now with
> an EPS file being gen
John - Thanks for the quick fix. I'm having a separate issue now with
an EPS file being generated (using savefig() again) that appears to be
invalid (can't display it in OS X Preview, or convert to PDF with
ps2pdf). Unfortunately, the code that creates this particular file is
rather involved,
On Wed, Jun 11, 2008 at 10:14 AM, John Hunter <[EMAIL PROTECTED]> wrote:
> Interesting. When I plot it on my screen it looks correct with a *Agg
> GUI backend. But when I save it (either from the GUI or using
> savefig) it has the problem you describe. This suggests to me that
> either some cac
On Mon, Jun 9, 2008 at 3:35 PM, Michael Hearne <[EMAIL PROTECTED]> wrote:
> savefig('textplot.eps')
> savefig('textplot.png')
> close(fig)
Interesting. When I plot it on my screen it looks correct with a *Agg
GUI backend. But when I save it (either from the GUI or using
savefig) it has the prob
I'm having a problem with the bbox keyword to the text() function. The
code below, for me, results in one postscript file that looks fine, but
the PNG file has letters outside of the bounding box for most of the
words I plot.
I'm using matplotlib '0.98pre' on Mac OS X.
import matplotlib
matpl
On Fri, 29 Feb 2008, David Huard apparently wrote:
> Have you tried pdfcrop ?
Did not know about it.
http://www.ctan.org/tex-archive/support/pdfcrop/>
Hmmm, is it legitimate to link to perl code here? ;-)
Thanks,
Alan
-
13 matches
Mail list logo