Use callback registry for all selector widgets #31042
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR summary
Addresses the core issue underlying: #24039
Prior to this you could only have one callback associated with the
onselectof any of the selectors which is limiting. This PR expands that to use a CallbackRegistry internally (like the other widgets) whcih allows handling multiple onselect callbacks.I used the name
on_selectinstead ofon_changedto differentiate from the value selection widgets vs these selectors. I also tried to keep back compat with the possible use case of directly assigning toonselect.For consistency with other widgets the selectors now also check for
self.eventsonbefore firing the callbacks🤖 Idea and direction by me. I used claude to do the typing. Iterated through several implement review cycles locally before posting
PR checklist