On Thu, Sep 9, 2010 at 4:13 AM, Eric Firing <efir...@hawaii.edu> wrote: > I don't think I understand the point you are making here--is it that the > Axes3D is a lone anomaly? >
Yes. And I feel that Axes3D better not add itself to the figure during the instance initialization. Just a different view of the current bug. > The main purpose of the changes I made was to clarify the tracking of axes > by having them internally listed in only one data structure instead of > always having to add or remove them from three separate structures. Fixing > the 3D bug was a side-effect. Whether the changes I made were a net > improvement, or a good design, remains debatable. Criticisms and > suggestions for improvement or replacement are welcome. > I think this is what need to be done and I think you did it right (thank you for your effort). I just wanted to raise a question of whether we let Axes3D add itself to its parent (although this is not a bug anymore). If you and others feel okay about it, then that's completely fine with me also. Regards, -JJ ------------------------------------------------------------------------------ This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
