Skip to content

document and test Arrow and FancyArrow #7213

Closed as not planned
Closed as not planned

Description

@dopplershift

See #6583.

The code is pretty crufty, there are no tests, and it's not clear at all what the units are for drawing these things.

Activity

  1. added
    API: changesChanges to the public API, typically requiring deprecation.
    on Oct 3, 2016
  2. added this to the milestone on Oct 3, 2016
  3. dstansby commented on Mar 6, 2017

    @dstansby
    Member

    Yes please. I was just about to open a bunch of issues for ax.arrow()...

  4. self-assigned this
    on Mar 6, 2017
  5. dstansby commented on Jun 17, 2017

    @dstansby
    Member

    Having another look into the whole arrow business(/mess), and it looks like Arrow and FancyArrow are arrows where all the vertices are rigidly fixed in data space, which I think is something useful to have.

  6. efiring commented on Jun 18, 2017

    @efiring
    Member

    Why is that useful? It makes them behave badly when anything changes the aspect ratio.

  7. dstansby commented on Jun 18, 2017

    @dstansby
    Member

    In response to the the original report, I'm happy to add tests, and I think it's now clear what the units are for drawing the arrows (#8770). They might not be the best way to draw an arrow in 99% of use cases, but as long as they're well documented (which I'm happy to do) I don't really see a need to get rid of them.

  8. modified the milestones: , on Jul 11, 2017
  9. added and removed
    API: changesChanges to the public API, typically requiring deprecation.
    on Jul 11, 2017
  10. changed the title [-]Deprecate Arrow and FancyArrow[/-] [+]document and test Arrow and FancyArrow[/+] on Jul 11, 2017
  11. removed their assignment
    on May 12, 2019
  12. github-actions commented on Mar 31, 2023

    @github-actions

    This issue has been marked "inactive" because it has been 365 days since the last comment. If this issue is still present in recent Matplotlib releases, or the feature request is still wanted, please leave a comment and this label will be removed. If there are no updates in another 30 days, this issue will be automatically closed, but you are free to re-open or create a new issue if needed. We value issue reports, and this procedure is meant to help us resurface and prioritize issues that have not been addressed yet, not make them disappear. Thanks for your help!

  13. added
    status: closed as inactiveIssues closed by the "Stale" Github Action. Please comment on any you think should still be open.
    on May 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Documentationstatus: closed as inactiveIssues closed by the "Stale" Github Action. Please comment on any you think should still be open.status: inactiveMarked by the “Stale” Github Actiontopic: arrow

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions