On Friday, July 1, 2011 at 00:58:14 (-0700) Alan W. Irwin writes: > Hi Maurice: > > I am addressing this specifically to you because you may have some > idea of why the line style choices were made the way they were from > your long history with PLplot, but I hope others here jump into this > discussion as well. [snip]
Sorry for the delayed response. I can't comment on the history of the line style choices except to say they have been that way since I first started working with PLplot in 1990 and I haven't touched them IIRC. I personally don't use them much -- solid & dashed (I think #3) lines is about it. I was never that impressed with the appearance of some of the higher numbered ones either. Since you're contemplating a change that (a) would look better but (b) introduce backward incompatibility, one "nice" way to handle it would be through line style "sets". The legacy set would be 0, the new set 1. Let it default to the new set but use an API call to switch back to the legacy set. That way you can also easily recover exact postscript results on test program output when you're trying to isolate an output regression. Just my two cents, I don't have a strong opinion either way. Down with the British! (happy 7/4 ;) -- Maurice LeBrun ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
