Re: [matplotlib-devel] marker color handling: matplotlibrc versus args and kwargs

2006-10-11 Thread Norbert Nemec
Eric Firing wrote: Norbert, The problem in r2790: I changed the default value in matplotlibrc to 'auto' and everything worked fine for me. I forgot that, of course, anybody updating from an older version, would still have the values 'blue' and 'black' in their matplotlibrc,

Re: [matplotlib-devel] marker color handling: matplotlibrc versus args and kwargs

2006-10-11 Thread Eric Firing
Norbert, Either I am not understanding you correctly, or we have fundamentally different views of the role of matplotlibrc values. The way I see it, function args and kwargs *always* override matplotlibrc values, which in turn *always* override built-in defaults. So in the example above, if

Re: [matplotlib-devel] marker color handling: matplotlibrc versus args and kwargs

2006-10-11 Thread Norbert Nemec
John Hunter wrote: Eric == Eric Firing [EMAIL PROTECTED] writes: This is, what is wanted in 99% of the cases and for every other case, a rcfile-option will not help anyway. Eric This sounds ideal to me--it makes everything simpler, both Eric in the code and

Re: [matplotlib-devel] marker color handling: matplotlibrc versus args and kwargs

2006-10-11 Thread Norbert Nemec
John Hunter wrote: Norbert == Norbert Nemec [EMAIL PROTECTED] writes: Norbert This functionality was never there, so nobody can miss Norbert it. Before my changes, the options in matplotlibrc only Norbert allowed to specify fixed colors for mfc and mec. This is

Re: [matplotlib-devel] marker color handling: matplotlibrc versus args and kwargs

2006-10-10 Thread Eric Firing
Norbert, The problem in r2790: I changed the default value in matplotlibrc to 'auto' and everything worked fine for me. I forgot that, of course, anybody updating from an older version, would still have the values 'blue' and 'black' in their matplotlibrc, which would not be overridden by