You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Doc]: xlim_changed and ylim_changed not listed with other events #30647
This needs better documentation, but the topic is a bit more complex than just adding to the list as these are slightly different topics: Axes events vs GUI events. Both use a CallbackRegistry but
Hi! I'd like to work on this. I'm planning to add a section that distinguishes
between Axes events (xlim_changed, ylim_changed) and GUI events with examples.
@shiivangr Thanks for your willingness to contribue. However, I think we'd need a more general section on callbacks see the linked cases above. I'm even unaware how systematically designed our use of callbacks is. It feels a bit bolted-on in some places.
I understand you'd like more comprehensive callback documentation. Is this the right scope for me as a new contributor? I'm happy to take on the challenge if you think it's manageable
The problem is I'm not clear that attaching the callback registries to all the objects is an architecture we want to pursue in the long run. Therefore, I'm not clear we want to advertize this in the docs more.
Marking this as “needs discussion” because, per #30647 (comment), we need to decide how much we want to advertise the various callback registries before anyone can write a PR.
Activity
timhoffm commentedon Oct 10, 2025
This needs better documentation, but the topic is a bit more complex than just adding to the list as these are slightly different topics: Axes events vs GUI events. Both use a
CallbackRegistrybutxlim_changed/ylim_changeddef handle_lim_change(ax: Axes)def handle_event(event: Event)We actually have a couple more callback registries: https://github.com/search?q=repo%3Amatplotlib%2Fmatplotlib+%2FCallbackRegistry%2F+path%3A*.py&type=code
shiivangr commentedon Oct 10, 2025
Hi! I'd like to work on this. I'm planning to add a section that distinguishes
between Axes events (xlim_changed, ylim_changed) and GUI events with examples.
timhoffm commentedon Oct 10, 2025
@shiivangr Thanks for your willingness to contribue. However, I think we'd need a more general section on callbacks see the linked cases above. I'm even unaware how systematically designed our use of callbacks is. It feels a bit bolted-on in some places.
shiivangr commentedon Oct 10, 2025
I understand you'd like more comprehensive callback documentation. Is this the right scope for me as a new contributor? I'm happy to take on the challenge if you think it's manageable
timhoffm commentedon Oct 10, 2025
The problem is I'm not clear that attaching the callback registries to all the objects is an architecture we want to pursue in the long run. Therefore, I'm not clear we want to advertize this in the docs more.
rcomer commentedon Apr 14, 2026
Marking this as “needs discussion” because, per #30647 (comment), we need to decide how much we want to advertise the various callback registries before anyone can write a PR.