Copyright © 2008, 2009 Arndt Roger Schneider
The Rtl_tabset interface is fashioned after the Tk Menu interface. Each tab must be named in advance –the Rtl_tabset follows an explicit naming convention.
Example 5.3. Rtl_tabset as a Window Manager
# Insert a tab resembling a window: .tabset add mywindow \ -foreground red \ -background white \ -text "My Child Window" -state normal; # Create the window after the tab, # similar to the Tk Menu interface. frame .tabset.mywindow # Force a visual refresh: .tabset redraw
The Example 5.3, “Rtl_tabset as a Window Manager” shows how to use the Rtl_tabset as a window manager. Again an explicit naming convention is being used.
Propagation from embedded pages can be channeled through the grid geometry manager. The controls on the different pages are managed by the outer dialog–they share the same parent window with the tabset-control. All the controls from all pages must be initial managed, then unmapped (hidden) from the dialog. »grid remove« performs this, but keeps the geometric informations. Example 5.4, “grid remove” shows how-to accomplish this with the grid geometry manager.
Although the Rtl_tabset supports this usage scenario. The resulting design is necessarily strange. The tabs of a tabset differ sharply from the other controls outside the multi-pages element, and thus create a significant distraction.
The AQUA® tabset design is the best choice for an embedded multi-pages element. It is possible to customize the tabs of a Rtl_tabset to resemble the AQUA® design. Using a radiobutton-group is however a superior solution. Use a gstripes radiobutton-group under every major windowing systems to do this. The radiobutton-group design is platform independent.