Hi,
I just updated my checkout to rev 6829, and it seems
lines.Line2D.set_pickradius
has been renamed to setpickradius. Is this a typo? get_pickradius still exists.
This is on line 318 in lines.py. Renaming it back to set_pickradius seems make
it work the way it used to.
Cheers,
Martin
I've noticed that the rcparams settings for patch.facecolor and
patch.endcolor is ignored by bar() and barh() (and therefore hist()),
always displaying as blue and black, respectively. Is this intentional?
I'm running matplotlib 0.87.3
The culprit:
def bar(self, left, height, width=0.8, bottom=0
Well, I seem to have really dove into this.
Here are 4 different patches against the latest svn of axes.py (rev
2495). Note that the rest of my install is the 0.87.3 release (I had to
copy over quiver.py to get the latest axes.py to work).
patch1 has the following changes to bar() and barh():
Hi John,
John Hunter wrote:
Most people prefer the center aligning behavior, at least those who
complained on the list about bar, so when I wrote barh I adopted
this. I tried to fix bar in the process, but ended up running into
some bugs when I tested John Gill's table demo, and so left it as e
John Hunter wrote:
> I can live with that -- did you test your work with the table_demo?
I just tried table_demo, looks good, bars are nicely centered (had to
set my rcparams axes.hold to True to get all four colours of bars).
I'm having trouble applying your patch because of the way the file
Whoops. Forgot to include the patches for CHANGELOG and API_CHANGES. I
updated barh_demo.py as well, and tested the rest of the bar demos.
Here's the combined patch against 2515.
Sorry for the hassle, I'm a bit new at this.
Cheers,
Martin
John Hunter wrote:
"Martin&qu
I noticed that Axes.errorbar() was being unnecessarily called by
Axes.bar(), due to improper handling of when xerr and yerr are passed as
None (the default). I don't think it was causing any bad behaviour, but
here's the patch nevertheless.
Cheers,
Martin
Index: lib/matplotlib/axes.py
===
Not sure if I'm crazy, but it seems the __init__.py file is missing from
my newly installed version 0.87.5. I installed from the
matplotlib-0.87.5.win32-py2.4.exe binary. I now get:
>>> import matplotlib
Traceback (most recent call last):
File "", line 1, in ?
ImportError: No module named ma
Yup, looks like the matplotlib-0.87.5.win32-py2.4.exe binary's been fixed.
Thanks!
Martin
Boyd Waters wrote:
> Try downloading again?
>
> I have not tried the windows binary, but a source tarball from this
> morning was strange.
>
> I pulled a 0.87.5 tarball this morning that had lots of perm
Not sure if this already exists, but here's an example file of how to
get a wx.ToolTip to pop up and report the current mouse position in data
coordinates over a MPL axes. Not sure if it's the best way of doing
this, but it seems to work really well for me. Perhaps it would be
useful to add thi
Here's an updated version. mpl.use('WXAgg') should come before importing
pylab.
Martin
Martin Spacek wrote:
Not sure if this already exists, but here's an example file of how to
get a wx.ToolTip to pop up and report the current mouse position in data
coordinates over a M
stray tooltips from hanging around.
Martin
Martin Spacek wrote:
Here's an updated version. mpl.use('WXAgg') should come before importing
pylab.
Martin
"""Example of how to use wx tooltips on a matplotlib figure window.
A tooltip pops up and tracks the mouse when th
> What is this supposed to give you. I get a Very long tooltip box with:
>
> tip with a
> long
> line and a newline
>
>
> In it.
>
> then, when the mouse starts moving, I get a tip that is just the right
> size to hold the two coords, each on their own line.
That initial tooltip never shows u
I've updated the docstring with a comment about display issues in wxGTK.
Martin
Martin Spacek wrote:
Not sure if this already exists, but here's an example file of how to
get a wx.ToolTip to pop up and report the current mouse position in data
coordinates over a MPL axes. Not sure i
Hello, just thought I should report two unexpected behaviours, which
took me a while to pinpoint:
1) errorbar() plots the points but not the errorbars if axes.hold==False
for those axes (in my case, due to it being set to False in rcParams)
2) when axes.hold is False, (again either set locally
I forgot to mention, I'm running 0.87.7 in windows with WxAgg.
Martin
Martin Spacek wrote:
> Hello, just thought I should report two unexpected behaviours, which
> took me a while to pinpoint:
>
> 1) errorbar() plots the points but not the errorbars if axes.hold==False
> f
Looking through colors.py, I noticed that most of the grey cnames use
the spelling 'gray' (the US standard I think), although 'lightgrey'
shows up as a valid name, while 'lightgray' does not. After looking
around the web a bit for what the correct html names are, I found most
sites display 'gra
> # add british equivs
> for k, v in cnames.items():
>if k.find('gray')>=0:
>k = k.replace('gray', 'grey')
>cnames[k] = v
Neat, that's a much better idea.
> Note that in pylab, you can get some extra information by doing
>
help(colors)
Thanks. I really like all the new
John Hunter wrote:
> Thanks for the suggestion -- I did this automagically with
# add british equivs
for k, v in cnames.items():
if k.find('gray')>=0:
k = k.replace('gray', 'grey')
cnames[k] = v
Just noticed that 'lightgrey' is still in the cnames dict, which means
that 'lig
It's been a few months since I've updated and compiled from svn. I got
this error today from rev 3926 (in winxp using msvc71):
>python setup.py build_ext --inplace --force
BUILDING MATPLOTLIB
matplotlib: 0.9
Sorry for the delay. I gave that a try, but it didn't help. Seems that
_MSC_VER is undefined as well...
Martin
Michael Droettboom wrote:
> Martin Spacek wrote:
>> It's been a few months since I've updated and compiled from svn. I got
>> this error today from r
experience on this list may have to look into this and have more to
offer.
Cheers,
Mike
Martin Spacek wrote:
Sorry for the delay. I gave that a try, but it didn't help. Seems that
_MSC_VER is undefined as well...
Martin
Michael Droettboom wrote:
Martin Spacek wrote:
It's been a few
Hello,
I was using the "configure subplots" dialog a lot recently to precisely
resize my plots, and I noticed that often when I changed a slider only
slightly (say by 1 pixel), the numeric value displayed next to the
slider wouldn't change, because its precision was too low. So, I
modified th
23 matches
Mail list logo
