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 the '.r' option that Stefan used. >>> >> This is not the first time matplotlibrc has bitten us, and it won't be >> the last... >> >> But *shouldn't* '.r' override a setting in matplotlibrc, regardless of >> what that setting is? I think it should have set the mfc, or preferably >> both the mfc and the mec. >> > OK, that would be an alternative solution: set both mfc and mec to > 'auto', whenever the color is specified using a format string. However, > this would mean that the rcfile options markeredgecolor and > markerfacecolor are often ignored, even if they were set on purpose. If > that is the case, one could just as well deactivate them completely and > prevent some confusion. >
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 the user writes "plot(x,y,'r.')", red dots should be plotted no matter what is in matplotlibrc. It should not depend on whether something is set to 'auto'. Eric ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
