matplotlib-devel Mailing List for matplotlib

Ian Thomas wrote:
> Eric,
> 
>> I hit a bug (segfault) in cntr.c that is likely related to your changes. It
>> is ID 2956378 in the tracker.
> 
> Attached is a patch file with a fix for this bug. I've also included
> a minimal test file to demonstrate the behaviour before and after the
> fix, along with a brief explanation which I can expand upon if you
> wish.
> 
> Ian
Ian,
Excellent! Applied in svn 8152. I also added your test case to the 
tracker and closed the bug. Thanks for the great work!
Eric

Here is a major patch for mplot3d. Here is a summary of the changes:
 * bug fix: placement of title in 3D plots to match 2D plot behavior (see nonecolortester.py to demonstrate)
 * bug fix: allow facecolors and edgecolors to be specified as 'none' in 3D scatter plots to match the 2D scatter plot behavior (see nonecolortester.py to demonstrate)
 * bug fix: allow all keyword arguments to be used in text3D (see modified example code text3d_demo.py)
 * bug fix: allow an array of colors to be passed into bar3d to specify the colors on a per-bar or per-face basis (see new example code hist3d_demo2.py)
 * bug fix: allow all keyword arguments to be used in bar3d (see new example code hist3d_demo2.py)
 * bug fix: allow 3d scatter plots with 3 or 4 points with colors specified (see colortester2.py to demonstrate)
 * new feature: new method to disable mouse rotation in 3D plots
 * new feature: allow mouse rotation and zoom buttons to be specified by user
 * new feature: new Z-order sorting heuristic to eliminate rendering issues for the common case of using bar3d to visualize a 2D histogram (see modified example code hist3d_demo.py)
 * new feature: new method text2D (see modified example code text3d_demo.py)
 * code cleanup: warn when canvas is None which disables mouse callbacks
 * code cleanup: document more methods in mplot3d
Thanks,
-Ben

On Tue, Feb 23, 2010 at 10:14 PM, Fernando Perez <fpe...@gm...> wrote:
> Final question: should I put the little demo code at the bottom that I
> used for testing this up in an example file? I put some of that in
> the docstring as an example, but not all to avoid clutter.
OK, since I know people are busy, I took silence as acquiescence.
Committed in r8151, please let me know if I messed anything up and
I'll try to fix it. I'm used to the numpy docstring standard, but I
tried to adapt it to the mpl one by looking at the rest of pyplot,
let me know if it needs fine-tuning.
Cheers,
f

Eric,
> I hit a bug (segfault) in cntr.c that is likely related to your changes. It
> is ID 2956378 in the tracker.
Attached is a patch file with a fix for this bug. I've also included
a minimal test file to demonstrate the behaviour before and after the
fix, along with a brief explanation which I can expand upon if you
wish.
Ian

On Sat, Feb 20, 2010 at 3:50 PM, Jae-Joon Lee <lee...@gm...> wrote:
>
>
> After quickly going through the mpl source (and in my experience), I
> think it is quite safe to assume that there is no master-slave
> relation among the shared axes.
>
>
>> One more, related question: is it possible/reasonable to share *both*
>> x and y axes?
>
> Yes, it is possible as I often do.
OK, thanks for the feedback. I've just finalized it here:
http://gfif.udea.edu.co/idf/indefero/www/index.php/p/mscomp-2010/source/tree/master/0217/figsubp.py
Knowing now that the sharing doesn't have an actual master/slave
relationship (like the existing examples suggest since they appear to
require an explicit index for sharing), the actual implementation was
really trivial in the end. It might be a good idea to clarify this in
the main docs, the current examples make axis sharing look harder than
it actually is (all those tricks with order creation I was playing are
completely unnecessary).
If you all like this API, I'm happy to push into the real svn repo.
Final question: should I put the little demo code at the bottom that I
used for testing this up in an example file? I put some of that in
the docstring as an example, but not all to avoid clutter.
Cheers,
f