John Hunter wrote: > On Sun, Jan 3, 2010 at 3:54 PM, Eric Firing <efir...@hawaii.edu> wrote: >> The only problem is that lines.color is the default for LineCollection and >> Line2D, both of which are fairly separate from Axes, so having them default >> to rcParams['axes.color_cycle'][0] seems a little odd. > > Yes, I was worrying about the same thing while cooking dinner :-) A > line can be added to a Figure or an Axes, so perhaps the default color > should not come from there. What about a module level attribute > matplotlib.colors.cycle by an rc param "colors.cycle" and then the > default Line2D and LineCollection color can default to > matplotlib.colors.cycle[0].
We could, but I don't see any advantage over leaving it the way I made it a few minutes ago, which leaves lines.color independent of the axes-level cycle. It seems to me that color-cycling is quite different from setting a default color for something like Line2D, and there is no reason they should be connected via the first element of a list. Maybe this would need to be revisited as part of the API layer redesign that you sketched out once, but that we still haven't gotten around to advancing. The idea of a rename to colors.cycle has some appeal, except that as it is used, it really is Axes-specific, and appears uniquely at the Axes level. Eric ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
