-
-
Notifications
You must be signed in to change notification settings - Fork 21.6k
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
TabContainer should use Tabs instead of reimplementing them #4512
Comments
Tabs is the class describing only the tab buttons on top of the TabContainer. There is no Container in the Tabs class, simply each tab sends a signal when an action happens on it: Thus, since Tabs buttons should only be used as such (ie. as "simple Button"s), Tabs class may itself have the container. I can take that one. |
Well I think the idea would be to keep TabContainer, but replace its own tab "buttons" by an instance of Tabs. |
Alright. I'm in ;) |
Any updates? |
From the recent discussions it's not clear if we want to keep both, delete one, or make them work together. There is a proposal for removal: godotengine/godot-proposals#2129 There are also several proposals for features in At any rate, there needs to be a proper proposal now for any change like that. So, closing. |
In the end, this was implemented for 4.0 by #58687. For the record, this old issue was superseded by the proposal godotengine/godot-proposals#2514 which the above PR implemented. |
As discussed today on IRC [0], TabContainer
scene/gui/tab_container.cpp
should be modified to rely on Tabsscene/gui/tabs.cpp
instead of reimplementing tabs itself.The Tabs class has grown to be feature-rich (though it could still use some cleanup even after #4506), so it should stay as the sole implementation.
[0] http://godot.eska.me/irc-logs/devel/2016-05-01.log
The text was updated successfully, but these errors were encountered: