Fix: TabBar/TabContainer can't start with all tabs deselected #108255
+24
−6
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.
TabBars
andTabContainers
were unable to start with no tabs selected, and couldn't properly retain their current tab value of "-1", also across editor restarts.Fix for Issue:
#108223
Cause
As the tabs were added to a TabBar (or children to a TabContainer) as the scene was set up, a bug in TabBar would always select tab index 0, even if deselection was enabled.
Repro (also in linked issue):
Before fix:
Fixed via:
A missing check for
deselect_enabled
was added inTabBar.cpp
on the code path when a first tab is added to an empty bar.After fix:
Tests:
Verified on Windows only via manual testing and
./bin/godot.windows.editor.x86_64.console.exe --test --test-case="*[TabBar]*"