Think of the component rendering action. If there was a similar action where you could choose the unique ID of a tabset and the set the tab that displays, you could create wizards with virtually unlimited formatting options. A wizard is basically a tabset with a hidden tab menu and buttons that navigate to other tabs of the tabset. So if there was an option in the tabset to hide the tab menu, you could create any manner of button anywhere on the page that could navigate the “wizard”. Use case would: think of a smart phone. You have a “Home” screen and it has icons or tiles of different shapes and sizes (depending on your smartphone). You click an icon and the menu disappears and just the content you want appears. Then you can go back to the home screen. This can be accomplished through rendering of components but that process would be streamlined if it could be don’t in a tabset instead of recreating a tabset like functionality through rendering components. Also, when you have a page include loaded on a page in a tabset and you navigate to another tab, the page include remains in memory so when you navigate back to the tab with the page include, it is exactly as you left it. If you recreate this through rendering components, when you hide the page include, it dumps it from memory and reloads it when you show it again. This causes you to lose your place if you were in the middle of something on the page include.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.