Re: [matplotlib-devel] Problems with new PyQt4 API

2011-03-03 Thread Martin Teichmann
Hi Benjamin, Hi List, sorry for the backwards patch, here the forward one: --- backend_qt4_orig.py 2011-03-02 16:16:38.257797767 +0100 +++ backend_qt4.py 2011-03-02 16:17:19.526831397 +0100 @@ -395,8 +395,9 @@

[matplotlib-devel] bug 3165422, color cycles even if kwarg 'color' is set

2011-03-03 Thread Maximilian Trescher
Hey, i just fixed this bug: http://sourceforge.net/tracker/?func=detail&aid=3165422&group_id=80706&atid=560720 It's a one-liner. I think it's overkill to start a pull request for it. --- a/lib/matplotlib/axes.py +++ b/lib/matplotlib/axes.py @@ -247,7 +247,7 @@ class _process_plot_var_args:

Re: [matplotlib-devel] Problems with new PyQt4 API

2011-03-03 Thread Benjamin Root
On Thu, Mar 3, 2011 at 3:15 AM, Martin Teichmann wrote: > Hi Benjamin, Hi List, > > sorry for the backwards patch, here the forward one: > > > --- backend_qt4_orig.py 2011-03-02 16:16:38.257797767 +0100 > +++ backend_qt4.py

Re: [matplotlib-devel] Problems with new PyQt4 API

2011-03-03 Thread Darren Dale
On Thu, Mar 3, 2011 at 9:36 AM, Benjamin Root wrote: > As for the sourceforge/github confusion, we are currently in a transition > phase.  Our repository is now hosted on github, but the official website and > trackers are still sourceforge.  Sorry for any confusion there.  The > (un)official new

Re: [matplotlib-devel] Problems with new PyQt4 API

2011-03-03 Thread Benjamin Root
On Thu, Mar 3, 2011 at 3:15 AM, Martin Teichmann wrote: > Hi Benjamin, Hi List, > > sorry for the backwards patch, here the forward one: > > > --- backend_qt4_orig.py 2011-03-02 16:16:38.257797767 +0100 > +++ backend_qt4.py

[matplotlib-devel] Bug in Draggable Legend

2011-03-03 Thread James Kitchen
Hi all, I found a small bug in the Draggable Legend feature when you single-click on a legend, but don't drag it. It raises a TypeError. Here's code to reproduce. Try dragging the legend, then single-click the legend. #!/usr/bin/env python import matplotlib as mpl import pylab fig = pylab.f

Re: [matplotlib-devel] Bug in Draggable Legend

2011-03-03 Thread Jae-Joon Lee
I just committed a change that I believe that fixes this problem. https://github.com/matplotlib/matplotlib/commit/be420a34031c9c50813bc5be5f01a3cfb49639a1 Regards, -JJ On Fri, Mar 4, 2011 at 12:58 AM, James Kitchen wrote: > Hi all, > > I found a small bug in the Draggable Legend feature when

Re: [matplotlib-devel] Bug in Draggable Legend

2011-03-03 Thread Benjamin Root
On Thu, Mar 3, 2011 at 10:30 AM, Jae-Joon Lee wrote: > I just committed a change that I believe that fixes this problem. > > > https://github.com/matplotlib/matplotlib/commit/be420a34031c9c50813bc5be5f01a3cfb49639a1 > > Regards, > > -JJ > > Confirmed that it fixes the problem for me on the GTKAgg

Re: [matplotlib-devel] Bug in Draggable Legend

2011-03-03 Thread James Kitchen
Looks like that fixed it. Thanks! Jim From: Benjamin Root To: Jae-Joon Lee Cc: James Kitchen ; matplotlib-devel@lists.sourceforge.net Sent: Thu, March 3, 2011 11:40:32 AM Subject: Re: [matplotlib-devel] Bug in Draggable Legend On Thu, Mar 3, 2011 at 10:3

[matplotlib-devel] patch to add legend.frameon to rcParams

2011-03-03 Thread Mike Kaufman
I noticed that this didn't exist and I never seem to want a frame anyway so here's a patch. I wasn't sure if anything in doc/ needed to be changed... I don't really like the name "legend.frameon". I'd rather have "legend.frame" or "legend.useframe". If people would accept changing the name of

Re: [matplotlib-devel] Problems with new PyQt4 API

2011-03-03 Thread Darren Dale
On Thu, Mar 3, 2011 at 10:22 AM, Benjamin Root wrote: > Just for completeness, I wanted to include a link to some sort of reference > indicating a need to change the function.  I can not find any documentation > that says that we need to change from getSaveFileName() to > getSaveFileNameAndFilter(

Re: [matplotlib-devel] Problems with new PyQt4 API

2011-03-03 Thread Benjamin Root
On Thursday, March 3, 2011, Darren Dale wrote: > On Thu, Mar 3, 2011 at 10:22 AM, Benjamin Root wrote: >> Just for completeness, I wanted to include a link to some sort of reference >> indicating a need to change the function.  I can not find any documentation >> that says that we need to change