Skip to content

equivalent of 'xlim_changed' for mpl_connect() #317

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.

Sign up for GitHub

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

Jump to bottom
Closed
ddale opened this issue Jun 20, 2011 · 2 comments
Closed

equivalent of 'xlim_changed' for mpl_connect() #317

ddale opened this issue Jun 20, 2011 · 2 comments
Assignees
@pelson
Labels
New feature status: closed as inactive Issues closed by the "Stale" Github Action. Please comment on any you think should still be open. status: inactive Marked by the “Stale” Github Action

Comments

@ddale
Copy link
Contributor

ddale commented Jun 20, 2011

Original report at SourceForge, opened Wed Aug 5 07:51:25 2009

The 'callback' events 'xlim_changed' and 'ylim_changed' are only available through the

callbacks.connect('xlim_changed',dostuff)

API and there does not seem to be anything equivalent in 'standard' mpl_connect() API. However, this is definitely something that would be very useful (execute a function/method when the view limits change in at least one of the axes)
@ghost ghost assigned pelson Jul 1, 2012
@petehuang
Copy link
Contributor

Hi,

This issue has been inactive for a while. Does this continue to represent a useful enhancement? If not, I recommend closing this issue. Thanks!

@tacaswell tacaswell modified the milestones: 2.1 (next point release), 2.2 (next next feature release) Sep 24, 2017
@jklymak jklymak removed the SF label Mar 7, 2018
Open
@github-actions
Copy link

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!

@github-actions github-actions bot added the status: inactive Marked by the “Stale” Github Action label Feb 27, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Mar 30, 2023
@tacaswell tacaswell removed this from the future releases milestone Mar 30, 2023
@rcomer rcomer added the status: closed as inactive Issues closed by the "Stale" Github Action. Please comment on any you think should still be open. label May 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@pelson pelson

Labels
New feature status: closed as inactive Issues closed by the "Stale" Github Action. Please comment on any you think should still be open. status: inactive Marked by the “Stale” Github Action
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@ddale @tacaswell @pelson @petehuang @jklymak @rcomer