Repository navigation
Collections could check x- and y- transforms separately to decide whether to autoscale each direction #15518
Description
Bug report
Consider the following example
from pylab import *
plt.rcdefaults()
fig, ax = plt.subplots()
ax.plot([1, 3], [5, 7])
ax.vlines(x=[1, 2, 3], ymin=0, ymax=1, transform=ax.get_xaxis_transform())
plt.show()where I want to use vlines in a manner similar to axvline, i.e. lines spanning the full axes height (but more efficiently than with repeated calls to axvline, as vlines will create a single LineCollection.
The autoscaling in the y axis incorrectly goes all the way down to include (0, 1) (coming from the call to vlines), even though these values are in axes coordinates rather than data coordinates.
In effect, I think this is equivalent to the suggestion at #13642 (comment).
Matplotlib version
- Operating system: linux
- Matplotlib version: master or 3.1
- Matplotlib backend (
print(matplotlib.get_backend())): any - Python version: 37
- Jupyter version (if applicable): no
- Other libraries:
Activity
github-actions commentedon Jun 28, 2023
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!
ksunden commentedon Jun 28, 2023
Fixed by #25324