Skip to content

Commit

Permalink
Apply automatic changes
Browse files Browse the repository at this point in the history
  • Loading branch information
cb1kenobi authored and github-actions[bot] committed Nov 9, 2024
1 parent 928b84e commit 843f455
Show file tree
Hide file tree
Showing 2 changed files with 10 additions and 1 deletion.
2 changes: 1 addition & 1 deletion docs/api/api.json
Original file line number Diff line number Diff line change
Expand Up @@ -186020,7 +186020,7 @@
],
"type": "object",
"editUrl": "https://github.com/appcelerator/titanium_mobile/edit/master/apidoc/Titanium/UI/TabGroup.yml",
"description": "| Android | iOS |\n| ------- | --- |\n| ![Android](./tabgroup_android.png) | |\n\nA tab group can contain one or more [Tab](Titanium.UI.Tab) objects, each of which has an\nassociated tab control that is used to bring it into focus.\n\nUse the <Titanium.UI.createTabGroup> method or **`<TabGroup>`** Alloy element to create a tab group\nthat, in turn, contains one or more `<Tab>` elements.\n\nYou can add tabs to the group using [addTab](Titanium.UI.TabGroup.addTab), and programmatically\nswitch to a specific tab using [setActiveTab](Titanium.UI.TabGroup.setActiveTab).\n\n#### Platform Implementation Notes\n\nWhen using a tab group, note the following differences between platforms:\n\n* The tab group controls are positioned at the top of the display on Android and at the bottom\non iOS.\n\n* On Android, only one tab group may exist at one time. A tab group may be closed to allow a new\none to be opened later, but the root of the application must be a heavyweight window to prevent\nit exiting. Tabs cannot be removed from the tab group once added, and tabs cannot be reordered.\n\n* On iOS, more than one tab group may exist, and may be opened and closed as required.\nEach tab can contain a stack of windows, and the user can switch between them by tapping the\ntab's associated control. Tabs can be removed, and the user may (optionally) be allowed to\nreorder tabs.\n\n* On iOS, it is also possible to add tabs by updating the\n[tabs](Titanium.UI.TabGroup.tabs) property, and to switch active tabs by setting the\n[active](Titanium.UI.Tab.active) property on one of the tabs to `true`. Since these mechanisms\nare platform-specific, it is recommended that you use `addTab` and `setActiveTab` instead.\n\n* If you use the iOS-specific mechanisms, it is possible to add multiple active tabs\nto a tab group. In this case, the result of which tab is initially selected is undefined.\n\n#### Further Reading\n\nIf using tab groups on iOS, see\n[iOS UI Element Usage Guidelines](https://developer.apple.com/ios/human-interface-guidelines/bars/tab-bars/).\n",
"description": "| Android | iOS |\n| ------- | --- |\n| ![Android](./tabgroup_android.png) | |\n\nA tab group can contain one or more [Tab](Titanium.UI.Tab) objects, each of which has an\nassociated tab control that is used to bring it into focus.\n\nUse the <Titanium.UI.createTabGroup> method or **`<TabGroup>`** Alloy element to create a tab group\nthat, in turn, contains one or more `<Tab>` elements.\n\nYou can add tabs to the group using [addTab](Titanium.UI.TabGroup.addTab), and programmatically\nswitch to a specific tab using [setActiveTab](Titanium.UI.TabGroup.setActiveTab).\n\n#### Platform Implementation Notes\n\nWhen using a tab group, note the following differences between platforms:\n\n* The tab group controls are positioned at the top of the display on Android and at the bottom\non iOS.\n\n* On Android, only one tab group may exist at one time. A tab group may be closed to allow a new\none to be opened later, but the root of the application must be a heavyweight window to prevent\nit exiting. Tabs cannot be removed from the tab group once added, and tabs cannot be reordered.\n\n* If you use a BottomNavigation on Android with a Material 3 theme you'll have to create a file\n`/app/platform/android/res/values/dimens.xml` and add to fix the height of the menu:\n```xml\n<?xml version=\"1.0\" encoding=\"utf-8\"?>\n<resources>\n <dimen name=\"design_bottom_navigation_height\">80dp</dimen>\n</resources>\n```\n\n* On iOS, more than one tab group may exist, and may be opened and closed as required.\nEach tab can contain a stack of windows, and the user can switch between them by tapping the\ntab's associated control. Tabs can be removed, and the user may (optionally) be allowed to\nreorder tabs.\n\n* On iOS, it is also possible to add tabs by updating the\n[tabs](Titanium.UI.TabGroup.tabs) property, and to switch active tabs by setting the\n[active](Titanium.UI.Tab.active) property on one of the tabs to `true`. Since these mechanisms\nare platform-specific, it is recommended that you use `addTab` and `setActiveTab` instead.\n\n* If you use the iOS-specific mechanisms, it is possible to add multiple active tabs\nto a tab group. In this case, the result of which tab is initially selected is undefined.\n\n#### Further Reading\n\nIf using tab groups on iOS, see\n[iOS UI Element Usage Guidelines](https://developer.apple.com/ios/human-interface-guidelines/bars/tab-bars/).\n",
"events": [
{
"name": "focus",
Expand Down
9 changes: 9 additions & 0 deletions docs/api/titanium/ui/tabgroup.md
Original file line number Diff line number Diff line change
Expand Up @@ -31,6 +31,15 @@ on iOS.
one to be opened later, but the root of the application must be a heavyweight window to prevent
it exiting. Tabs cannot be removed from the tab group once added, and tabs cannot be reordered.

* If you use a BottomNavigation on Android with a Material 3 theme you'll have to create a file
`/app/platform/android/res/values/dimens.xml` and add to fix the height of the menu:
```xml
<?xml version="1.0" encoding="utf-8"?>
<resources>
<dimen name="design_bottom_navigation_height">80dp</dimen>
</resources>
```

* On iOS, more than one tab group may exist, and may be opened and closed as required.
Each tab can contain a stack of windows, and the user can switch between them by tapping the
tab's associated control. Tabs can be removed, and the user may (optionally) be allowed to
Expand Down

0 comments on commit 843f455

Please sign in to comment.