2.2.41 tabSet (Contextual Tab Set)
This element specifies a contextual tab set control. As the id and idQ attributes are not present, this element can only be used to refer to existing built-in tab sets. This element cannot be used to create new contextual tab sets.
For example, consider the following XML fragment:
-
<tabSet idMso="TabSetPictureTools"> <tab id="tab" label="Custom Tab"> … </tab> </tabSet>
This XML fragment is used to add a new custom tab to the tab set with an identifier of "TabSetPictureTools".
The following table summarizes the elements that are parents of this element.
|
Parent Elements |
|---|
|
contextualTabs (section 2.2.10) |
The following table summarizes the child elements of this element.
|
Child Elements |
Subclause |
|---|---|
|
tab (Tab) |
section 2.2.39 |
The following table summarizes the attributes of this element.
|
Attributes |
Description |
|---|---|
|
getVisible (getVisible callback) |
Specifies the name of a callback function to be called to determine the visibility state of this control. The getVisible and visible attributes are mutually exclusive. If neither attribute is specified, the control SHOULD default to being visible. For example, consider the following XML fragment:
In this example, the IsButtonVisible callback function is called when the application needs to determine the visibility of the button. The possible values for this attribute are defined by the ST_Delegate simple type, as specified in section 2.3.2. |
|
idMso (built-in control identifier) |
Specifies the identifier of a built-in control. The contents of this attribute are application-defined. For example, consider the following XML fragment:
This is used to create a clone of the control with an identifier of "Bold". The possible values for this attribute are defined by the ST_ID simple type, as specified in section 2.3.5. |
|
visible (control visibility) |
Specifies the visibility state of the control. The getVisible and visible attributes are mutually exclusive. If these attributes are omitted, the control SHOULD default to being visible. For example, consider the following XML fragment:
In this example, the built-in tab with an identifier of "TabHome" is hidden. The possible values for this attribute are defined by the XML schema boolean datatype. |
The following XML schema fragment defines the contents of this element:
-
<xsd:complexType name="CT_TabSet"> <xsd:sequence> <xsd:element name="tab" type="CT_Tab" minOccurs="0" maxOccurs="50"/> </xsd:sequence> <xsd:attribute name="idMso" type="ST_ID" use="required"/> <xsd:attributeGroup ref="AG_Visible"/> </xsd:complexType>