-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
Make Radio Button behaviour modular and consistent with other widgets #21294
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.
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
Merged
alice-i-cecile
merged 6 commits into
bevyengine:main
from
PPakalns:radio_button_improvement
Oct 13, 2025
Merged
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
dbc1432
Make Radio Button behaviour modular and consistent with other widgets
PPakalns 434353c
Fix bug with event propagation cancellation
PPakalns 72b5690
Added release note for radio group and button widget improvements
PPakalns 40d2d46
Fix markdown linter error
PPakalns 1ecf910
Markdown lint fix, attempt 2
PPakalns c0cc34f
Merge branch 'main' into radio_button_improvement
alice-i-cecile File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
20 changes: 20 additions & 0 deletions
20
release-content/release-notes/radio_group_and_button_widget_improvements.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,20 @@ | ||
| --- | ||
| title: "`RadioButton`, `RadioGroup` widget minor improvements" | ||
| authors: ["@PPakalns"] | ||
| pull_requests: [21294] | ||
| --- | ||
|
|
||
| `RadioButton` and `RadioGroup` usage remains fully backward compatible. | ||
|
|
||
| Improvements: | ||
|
|
||
| - Event propagation from user interactions will now be canceled even if | ||
| widgets are disabled. Previously, some relevant event propagation | ||
| was not properly canceled. | ||
| - `RadioButton` now emits a `ValueChange<bool>` entity event when checked, | ||
| even when checked via a `RadioGroup`. Consistent with other `Checkable` widgets. | ||
| As a `RadioButton` cannot be unchecked through direct user interaction with this widget, | ||
| a `ValueChange` event with value `false` can not be triggered for `RadioButton`. | ||
| - If a `RadioButton` is focusable, a value change event can be triggered | ||
| using the **Space** or **Enter** keys when focused. | ||
| - `RadioGroup` is now optional and can be replaced with a custom implementation. |
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems like an odd way to use
ValueChange:true), then we should triggerActivateinstead.Activateis meant for widgets whose state never changes.ValueChange(false)when the button gets deselected because of mutual exclusion. However, that's more complicated because now you would have to pass around the entity id of the previously checked button (which is not a problem here, but might be further down).More generally, if we're going to use
ValueChange, it should always reflect the current state of the widget triggering it: a listener that only listens toValueChangeshould always know what state the source is in. We can't do this if it only sendsValueChangefor some state transitions and not others.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can use
Activate. But i usedValueChangeinstead because all other Checkable widgets raise ValueChange event.And for me it seemed logical to think that RadioButton can only be checked by interacting with it. To uncheck it users need to add other widgets / radio group / logic that can uncheck it.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So I would prefer
ValueChange<bool>because all checkable widgets use that event.EDIT: P.S. But activate is fine with me too.