matplotlib-users Mailing List for matplotlib

In 0.61.0, when plotting a simple array with error bars, the default color of 
the error bars is black, instead of being the same as the line/markers color, 
e.g.:
>>> errorbar([1,2,3,4,5],[3,4,5,6,7],fmt='ro',yerr=[1,1,1,1,1])
I prefer them to be the same, especially since the default color for marker/line 
is blue and a beginner may be surprised to see the different color.
This may be related to my last posting regarding the (default) marker edge 
color.
JC Hsu

In 0.61.0, the marker edge color is still black, instead of being the same as 
the marker face color. Personally, I think they should be the same. What do 
people think?
One reason for the same color argument is that if the markersize is set to a 
small value, it will show mostly the edge color.
One possible reason against it is that if the marker color is white (or whatever 
the background color is), then you can't see the marker. But we can default 
this case to black (or whatever).
JC Hsu

Hi John:
When using the errorbar(), I have no way to change the marker size (except do a 
separate plot()). Should we add that to the errorbar's argument list?
Also there is another inconsistency between plot() and errorbar(), the latter 
needs the fmt argument, but the former does not recognize it.
Another comment about errorbar() is that the error bar should not show in the 
marker face area, i.e the error bars should be drawn first and then the markers 
with no transparency.
JC Hsu

----- Original Message ----- 
From: "John Hunter" <jdh...@ac...>
> >>>>> "Gary" == Gary Pajer <pa...@in...> writes:
> 
> Gary> I've poked around the docs and archives, for a clue to this,
> Gary> but if it's there I didn't recognize it.
> 
> Gary> version: 0.62 WinXP default backend: TkAgg interactive (with
> Gary> ipython)
> 
> Hi Gary, just to make sure we're clear. The last version of
> matplotlib released was 0.61.0. Is this what you mean, or are you
> using CVS?
0.61.0 (my typo)
> 
> Gary> On computer A I have version 0.54 installed. There I can
> Gary> create a plot and say savefig('plot.eps') and get a good eps
> Gary> file.
> 
> Gary> On computer B I have version 0.62 installed. There I can
> Gary> create a plot and say savefig('plot.eps') with different
> Gary> results: ghostscript chokes.
> 
> There is a known bug in the ps backend on win32 that was discussed
> here a couple of weeks ago. Fortunately, it has a trivial fix. In
> site-packages/matplotlib/backends/backend_ps.py, in the encodeTTFasPS
> function, replace the line
> 
> font = file(fontfile)
> 
> with
> 
> font = file(fontfile, 'rb')
> 
> Windows cares a lot about that binary flag.
> 
> Please let me know if this cures what ails you, because we are getting
> ready to release the next matplotlib version and I hate to release
> code with known bugs.
That was it. Problem solved.
I remember that thread now. It didn't sink in at the time. Thanks, Gary
> 
> Thanks!
> JDH

>>>>> "Gary" == Gary Pajer <pa...@in...> writes:
 Gary> I've poked around the docs and archives, for a clue to this,
 Gary> but if it's there I didn't recognize it.
 Gary> version: 0.62 WinXP default backend: TkAgg interactive (with
 Gary> ipython)
Hi Gary, just to make sure we're clear. The last version of
matplotlib released was 0.61.0. Is this what you mean, or are you
using CVS?
 Gary> On computer A I have version 0.54 installed. There I can
 Gary> create a plot and say savefig('plot.eps') and get a good eps
 Gary> file.
 Gary> On computer B I have version 0.62 installed. There I can
 Gary> create a plot and say savefig('plot.eps') with different
 Gary> results: ghostscript chokes.
There is a known bug in the ps backend on win32 that was discussed
here a couple of weeks ago. Fortunately, it has a trivial fix. In
site-packages/matplotlib/backends/backend_ps.py, in the encodeTTFasPS
function, replace the line
 font = file(fontfile)
with
 font = file(fontfile, 'rb')
Windows cares a lot about that binary flag.
Please let me know if this cures what ails you, because we are getting
ready to release the next matplotlib version and I hate to release
code with known bugs.
Thanks!
JDH

I've poked around the docs and archives, for a clue to this, but if it's
there I didn't recognize it.
version: 0.62
WinXP
default backend: TkAgg
interactive (with ipython)
On computer A I have version 0.54 installed. There I can create a plot and
say
savefig('plot.eps')
and get a good eps file.
On computer B I have version 0.62 installed. There I can create a plot and
say
savefig('plot.eps')
with different results: ghostscript chokes.
In the case of computer A, the eps file contains
/NewCenturySchlbk-Roman findfont
while in the case of computer B, the file contains instead
/BitstreamVeraSerif-Roman findfont
both have TTFPATH=c:\windows\fonts
it's *possible* (I don't remember exactly) that I installed 0.61 from a
windows installer, and 0.54 from setup.py.
afaik, the .matplotlibrc are the same (at least in the font section)
computer B contains a file .ttffile.cache, while computer A does not have
this file
Removing it from B doesn't make any difference.
any idea ... ?
-gary