-
-
Notifications
You must be signed in to change notification settings - Fork 7.9k
Inconsistent linestyle specifications between Line2D and Patch artists #2136
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
👍 |
Hi. I would like to look into this issue. I am fairly new to Python and would love to take this opportunity to learn more about contributing to Python open-source projects. |
That would be great! This one will be a toughie. Not only will it require We have a developer guide on our website that gives a basic idea on how to |
Thanks. I will look into the developer guide. |
ninjasoul are you still looking into this? |
lennart0901 go ahead. I've not been able to pursue this. |
The api is rather inconsistent with respect to linestyles and dash patterns.
How much backward compatibility should be preserved? To me it makes most sense to change either the collections or lines to reflect the same style, either convert to dashes or have a dashes property... |
I would go with the approach of letting both forms of the linestyle I wouldn't worry about patches at the moment. On Tue, Jul 15, 2014 at 5:44 AM, lennart0901 notifications@github.com
|
It did not mean I want to remove any way one can specify line/dash-patterns. |
Just noticed that to get a dashed line in a line plot:
is completely different from how to specify a line style elsewhere, such as bar():
It would make sense to me to normalize these two specifications together so that either "accent" of linestyle specifications would work anywhere a "linestyle" argument is accepted.
The text was updated successfully, but these errors were encountered: