-
Notifications
You must be signed in to change notification settings - Fork 17
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
Separate widgets for tabs and content areas #13
Comments
Hi @ngugcx ! Sorry. I didn't really understand the problem. Could you describe it with an example? Are you wanting to change the gap between content areas and tabs? If so, you can change the theme with something like this: TabbedViewTheme(
child: tabbedView,
data: TabbedViewThemeData(
tabsArea: TabsAreaThemeData(color: Colors.yellow),
contentArea: ContentAreaThemeData(
padding: EdgeInsets.zero,
decoration: BoxDecoration(color: Colors.blue)))); It is also possible to have different settings for the selected tab. So only this one can have an extra gap. |
Like Chrome, the tabs can be put together with the min/max/close buttons, and the content area can be put somewhere else. They are separated widgets, not tightly connected with each other in UI. Just like the relationship of the Qt widgets, QTabBar and QStackedWidget. |
Cool, got it. The current component doesn't allow instantiating its parts as separate widgets. I didn't think of that use case. I need to think about how I could do that. |
Probably the biggest problem would be the dropdown menu. |
Sometimes tab_area and content_area are not placed together.
It will be more flexiable if they can be seperated.
The text was updated successfully, but these errors were encountered: