Skip to content

list of markers in documentation could be improved #7342

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

Closed
3 of 6 tasks
anntzer opened this issue Oct 25, 2016 · 3 comments · Fixed by #11437
Closed
3 of 6 tasks

list of markers in documentation could be improved #7342

anntzer opened this issue Oct 25, 2016 · 3 comments · Fixed by #11437

Comments

@anntzer
Copy link
Contributor

anntzer commented Oct 25, 2016

The table at the top of http://matplotlib.org/devdocs/api/markers_api.html could be improved.

  • The curly quotes are sometimes in the wrong direction (probably just wrap everything in backquotes).
  • What's the difference between "triangle_down" and "tri_down", if any? It may be better to actually just draw the markers in the table (possibly using some resembling unicode characters, to keep things simpler?).
  • How do I specify TICKLEFT, CARETLEFT and friends? (and again I have no ideas how these markers look like)
  • The various "nothing" entries could be merged together.
  • What does "the size is normalized" mean for verts? Single x/y rescaling so that the max size (between x and y) is equal to whatever?
  • The (numsides, style, angle) entry could easily fit within the table itself (not sure how easy this is to do with rst though.
@petehuang
Copy link
Contributor

@tacaswell tacaswell added this to the 2.0.1 (next bug fix release) milestone Jan 7, 2017
@QuLogic
Copy link
Member

QuLogic commented Jan 7, 2017

I copied that information into the original post; that will give the issue a proper progress bar in the issue listing.

@QuLogic QuLogic modified the milestones: 2.0.1 (next bug fix release), 2.0.2 (next bug fix release) May 3, 2017
@tacaswell tacaswell modified the milestones: 2.1.1 (next bug fix release), 2.2 (next feature release) Oct 9, 2017
@ImportanceOfBeingErnest
Copy link
Member

I tackled the remaining open points in #11437.

@story645 story645 removed this from the future releases milestone Oct 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants