Not planned
Description
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.
{{ message }}
No one assigned
No type
No projects
None yet
No branches or pull requests
Activity
dstansby commentedon Mar 6, 2017
Yes please. I was just about to open a bunch of issues for
ax.arrow()...dstansby commentedon Jun 17, 2017
Having another look into the whole arrow business(/mess), and it looks like
ArrowandFancyArroware arrows where all the vertices are rigidly fixed in data space, which I think is something useful to have.efiring commentedon Jun 18, 2017
Why is that useful? It makes them behave badly when anything changes the aspect ratio.
dstansby commentedon Jun 18, 2017
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.
[-]Deprecate Arrow and FancyArrow[/-][+]document and test Arrow and FancyArrow[/+]4 remaining items