2.3.25 CT_ButtonGroup

Target namespace: http://schemas.microsoft.com/office/2009/07/customui

Referenced by: CT_Box, CT_Group

Specifies a grouping container that visually groups child controls together.

Child Elements:

control: A CT_ControlCloneRegular element, as specified in section 2.3.38.

button: A CT_ButtonRegular element, as specified in section 2.3.26.

toggleButton: A CT_ToggleButtonRegular element, as specified in section 2.3.84.

gallery: A CT_GalleryRegular element, as specified in section 2.3.46.

menu: A CT_MenuRegular element, as specified in section 2.3.57.

dynamicMenu: A CT_DynamicMenuRegular element, as specified in section 2.3.43.

splitButton: A CT_SplitButtonRegular element, as specified in section 2.3.71.

separator: A CT_Separator element, as specified in section 2.3.67.

Attributes:

id: An ST_UniqueID attribute, as specified in section 2.4.27, that specifies the identifier of a custom control. All custom controls MUST have unique identifiers. The id, idQ, and idMso attributes are mutually exclusive. Exactly one of these attributes MUST be specified on all controls.

idQ: An ST_QID attribute, as specified in section 2.4.22, that specifies the qualified identifier of a control. This attribute is used to reference controls or containers created by other Custom UI documents. The id, idQ, and idMso attributes are mutually exclusive. Exactly one of these attributes MUST be specified on all controls.

tag: An ST_String attribute, as specified in section 2.4.24, that specifies an arbitrary string that provides additional information about this control during callback function calls. If this attribute is omitted, the value defaults to an empty string.

visible: A Boolean attribute that specifies the visibility state of this control. The visible and getVisible attributes are mutually exclusive. They MUST NOT be used together. If neither attribute is specified, the control defaults to being visible.

getVisible: An ST_Delegate attribute that specifies the name of a callback function that is called to determine the visibility state of this control. The visible and getVisible attributes are mutually exclusive. They MUST NOT be used together. If neither attribute is specified, the control defaults to being visible.

insertAfterMso: An ST_ID attribute that specifies the identifier of a built-in control after which this control will be inserted. The insertAfterMso, insertAfterQ, insertBeforeMso, and insertBeforeQ attributes are mutually exclusive. They MUST NOT be used together. If none of these attributes is specified, the controls will be appended to the existing set of controls, in the order they are defined in the XML.

insertBeforeMso: An ST_ID attribute that specifies the identifier of a built-in control before which this control will be inserted. The insertAfterMso, insertAfterQ, insertBeforeMso, and insertBeforeQ attributes are mutually exclusive. They MUST NOT be used together. If none of these attributes is specified, the controls will be appended to the existing set of controls, in the order they are defined in the XML.

insertAfterQ: An ST_QID attribute, as specified in section 2.4.22, that specifies the qualified identifier of a control after which this control will be inserted. The insertAfterMso, insertAfterQ, insertBeforeMso, and insertBeforeQ attributes are mutually exclusive. They MUST NOT be used together. If none of these attributes is specified, the controls will be appended to the existing set of controls, in the order they are defined in the XML.

insertBeforeQ: An ST_QID attribute that specifies the qualified identifier of a control before which this control will be inserted. The insertAfterMso, insertAfterQ, insertBeforeMso, and insertBeforeQ attributes are mutually exclusive. They MUST NOT be used together. If none of these attributes is specified, the controls will be appended to the existing set of controls, in the order they are defined in the XML.

The following W3C XML Schema ([XMLSCHEMA1/2] section 2.1) fragment specifies the contents of this complex type.

 <xsd:complexType name="CT_ButtonGroup">
   <xsd:sequence>
     <xsd:choice minOccurs="0" maxOccurs="1000">
       <xsd:element name="control" type="CT_ControlCloneRegular"/>
       <xsd:element name="button" type="CT_ButtonRegular"/>
       <xsd:element name="toggleButton" type="CT_ToggleButtonRegular"/>
       <xsd:element name="gallery" type="CT_GalleryRegular"/>
       <xsd:element name="menu" type="CT_MenuRegular"/>
       <xsd:element name="dynamicMenu" type="CT_DynamicMenuRegular"/>
       <xsd:element name="splitButton" type="CT_SplitButtonRegular"/>
       <xsd:element name="separator" type="CT_Separator"/>
     </xsd:choice>
   </xsd:sequence>
   <xsd:attributeGroup ref="AG_IDCustom"/>
   <xsd:attributeGroup ref="AG_Visible"/>
   <xsd:attributeGroup ref="AG_PositionAttributes"/>
 </xsd:complexType>

See section 5.1 for the full W3C XML Schema ([XMLSCHEMA1/2] section 2.1).