UI Automation Support for the Toolbar Control Type
This topic provides information about UI Automation support for the Toolbar control type. In UI Automation, a control type is a set of conditions that a control must meet in order to use the ControlTypeProperty property. The conditions include specific guidelines for UI Automation tree structure, UI Automation property values and control patterns. Toolbar controls enable end users to activate commands and tools contained within a application.
The following sections define the required UI Automation tree structure, properties, control patterns, and events for the Toolbar control type. The UI Automation requirements apply to all toolbar controls, whether Windows Presentation Foundation (WPF), Win32, or Windows Forms.
This topic contains the following sections.
- Required UI Automation Tree Structure
- Required UI Automation Properties
- Required UI Automation Control Patterns
- Required UI Automation Events
- Related Topics
Required UI Automation Tree Structure
The following table depicts the control view and the content view of the UI Automation tree that pertains to toolbar controls and describes what can be contained in each view. For more information on the UI Automation tree, see UI Automation Tree Overview.
| Control View | Content View |
|---|---|
|
|
A toolbar control can contain any type of control within its subtree. They most often contain buttons, combo boxes, and split buttons.
Required UI Automation Properties
The following table lists the UI Automation properties whose value or definition is especially relevant to toolbar controls. For more information on UI Automation properties, see UI Automation Properties for Clients.
| UI Automation Property | Value | Notes |
|---|---|---|
See notes. |
The value of this property needs to be unique across all controls in an application. |
|
See notes. |
The outermost rectangle that contains the whole control. |
|
See notes. |
Supported if there is a bounding rectangle. If not every point within the bounding rectangle is clickable, and you perform specialized hit testing, then override and provide a clickable point. |
|
See notes. |
If the control can receive keyboard focus, it must support this property. |
|
Depends |
The Toolbar control does not need a name unless more than one is used within an application. If more than one is present, each must have a distinguishing name (for example, Formatting or Outlining). |
|
Null |
Toolbar controls never have a label. |
|
Toolbar |
This value is the same for all UI frameworks. |
|
"toolbar" |
Localized string corresponding to the Toolbar control type. |
|
True |
The Toolbar control is always content. |
|
True |
The Toolbar control must always be a control. |
Required UI Automation Control Patterns
The following table lists the UI Automation control patterns required to be supported by toolbar controls. For more information on control patterns, see UI Automation Control Patterns Overview.
| Control Pattern/Pattern Property | Support/Value | Notes |
|---|---|---|
Depends |
If the toolbar can be expanded and collapsed to show more items, then it must support this pattern. |
|
Depends |
If the toolbar can be docked to different parts of the screen, then it must support this pattern. |
|
Depends |
If the toolbar can be resized, rotated, or moved, it must support this pattern. |
Required UI Automation Events
The following table lists the UI Automation events required to be supported by all toolbar controls. For more information on events, see UI Automation Events Overview.
| UI Automation Event | Support | Notes |
|---|---|---|
BoundingRectangleProperty property-changed event. |
Required |
None |
IsOffscreenProperty property-changed event. |
Required |
None |
IsEnabledProperty property-changed event. |
Required |
None |
ExpandCollapseStateProperty property-changed event. |
Depends |
None |
Required |
None |
|
Required |
None |