次の方法で共有


SplitButtonRegular Class

Defines the SplitButtonRegular Class.This class is only available in Office2010.When the object is serialized out as xml, its qualified name is mso14:splitButton.

Inheritance Hierarchy

System.Object
DocumentFormat.OpenXml.OpenXmlElement
DocumentFormat.OpenXml.OpenXmlCompositeElement
DocumentFormat.OpenXml.Office2010.CustomUI.SplitButtonRegular

Namespace: DocumentFormat.OpenXml.Office2010.CustomUI
Assembly: DocumentFormat.OpenXml (in DocumentFormat.OpenXml.dll)

Syntax

'宣言
<ChildElementInfoAttribute(GetType(VisibleButton), FileFormatVersions.Office2010)> _
<OfficeAvailabilityAttribute(FileFormatVersions.Office2010)> _
<ChildElementInfoAttribute(GetType(VisibleToggleButton), FileFormatVersions.Office2010)> _
<ChildElementInfoAttribute(GetType(MenuRegular), FileFormatVersions.Office2010)> _
Public Class SplitButtonRegular _
    Inherits OpenXmlCompositeElement
'使用
Dim instance As SplitButtonRegular
[ChildElementInfoAttribute(typeof(VisibleButton), FileFormatVersions.Office2010)]
[OfficeAvailabilityAttribute(FileFormatVersions.Office2010)]
[ChildElementInfoAttribute(typeof(VisibleToggleButton), FileFormatVersions.Office2010)]
[ChildElementInfoAttribute(typeof(MenuRegular), FileFormatVersions.Office2010)]
public class SplitButtonRegular : OpenXmlCompositeElement

Remarks

The following table lists the possible child types:

  • VisibleButton <mso14:button>

  • VisibleToggleButton <mso14:toggleButton>

  • MenuRegular <mso14:menu>

2.3.28 CT_SplitButtonRegular

Target namespace: https://schemas.microsoft.com/office/2007/10/customui

Referenced by: CT_MenuRegular, CT_Menu, CT_SplitButton, CT_ButtonGroup, CT_ContextMenu

Specifies a split button control which is of fixed size because of its location. It otherwise is identical to the CT_SplitButton complex type.

Child Elements:

button : A CT_VisibleButton element.

toggleButton : A CT_VisibleToggleButton element.

menu : A CT_MenuRegular element.

Attributes:

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

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

id : An ST_UniqueID attribute that specifies the identifier of a custom control. All custom controls MUST have unique IDs. 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 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.

idMso : An ST_ID attribute that specifies the identifier of a built-in control. The id, idQ and idMso attributes are mutually exclusive. Exactly one of these attributes MUST be specified.

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

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

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 of these attributes are specified, then the control defaults to being visible.

getVisible : An ST_Delegate attribute that specifies the name of a callback function which 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 of these attributes are specified, the control defaults to being visible.

keytip : An ST_Keytip attribute that specifies a string which is displayed as the KeyTip for this control. The keytip and getKeytip attributes are mutually exclusive. They MUST NOT be used together. If neither of these attributes are specified, a KeyTip is not displayed.

getKeytip : An ST_Delegate attribute that specifies the name of a callback function which is called to determine the KeyTip for this control. The keytip and getKeytip attributes are mutually exclusive. They MUST NOT be used together. If neither of these attributes are specified, a KeyTip is not displayed.

showLabel : A boolean attribute that specifies whether the label for this control will be displayed. The showLabel and getShowLabel attributes are mutually exclusive. They MUST NOT be used together. If neither of these attributes are specified, the label of the control will be displayed.

getShowLabel : An ST_Delegate attribute that specifies the name of a callback function which is called to determine whether to display the label of this control. The showLabel and getShowLabel attributes are mutually exclusive. They MUST NOT be used together. If neither of these attributes are specified, the label of the control will be displayed.

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

<xsd:complexType name="CT_SplitButtonRegular">

<xsd:complexContent>

<xsd:extension base="CT_SplitButtonRestricted">

<xsd:sequence minOccurs="0">

<xsd:choice minOccurs="0">

<xsd:element name="button" type="CT_VisibleButton"/>

<xsd:element name="toggleButton" type="CT_VisibleToggleButton"/>

</xsd:choice>

<xsd:element name="menu" type="CT_MenuRegular"/>

</xsd:sequence>

</xsd:extension>

</xsd:complexContent>

</xsd:complexType>

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

Thread Safety

Any public static (Shared in Visual Basic) members of this type are thread safe. Any instance members are not guaranteed to be thread safe.

See Also

Reference

SplitButtonRegular Members

DocumentFormat.OpenXml.Office2010.CustomUI Namespace