UI Automation Support for the Calendar Control Type
Note
This documentation is intended for .NET Framework developers who want to use the managed UI Automation classes defined in the System.Windows.Automation namespace. For the latest information about UI Automation, see Windows Automation API: UI Automation.
This topic provides information about UI Automation support for the Calendar 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, control patterns, and UI Automation events.
Calendar controls allow a user to easily determine the date and select other dates.
The following sections define the required UI Automation tree structure, properties, control patterns, and events for the Calendar control type. The UI Automation requirements apply to all calendar 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 calendar 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 |
|---|---|
Calendar
|
Calendar
|
Calendar controls can be represented in many different forms within the user interface. The only guaranteed controls to be in the control view of the UI Automation tree are the data grid, header, header item, and list item controls.
Required UI Automation Properties
The following table lists the UI Automation properties whose value or definition is especially relevant to the calendar 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. |
|
Calendar |
This value is the same for all UI frameworks. |
|
True |
The calendar control is always included in the content view of the UI Automation tree. |
|
True |
The calendar control is always included in the control view of the UI Automation tree. |
|
See notes. |
If the control can receive keyboard focus, it must support this property. |
|
See notes. |
The label of the document control. Typically, the title of the document is used. |
|
"calendar" |
Localized string corresponding to the Calendar control type. |
|
See notes. |
The calendar control typically gets its name from the current day’s date. |
Required UI Automation Control Patterns
The following table lists the UI Automation control patterns required to be supported by all calendar controls. For more information on control patterns, see UI Automation Control Patterns Overview.
Control Pattern/Pattern Property |
Support |
Notes |
|---|---|---|
Yes |
The calendar control always supports the Grid pattern because the days within a month are items that can be navigated spatially. |
|
Depends |
Most calendar controls support flipping the view by page. The Scroll pattern is recommended in order to support paging navigation. |
|
Depends |
Most calendar controls retain a specific day, month, or year as a selection of the sub-element. Some calendars are multi-selectable and others only single-selectable. |
|
Yes |
The calendar control always has a header within its subtree for the days of the week, so the Table pattern must be supported. |
|
No |
The Value control pattern is not necessary for calendar controls because you cannot set the value directly on the control. If a specific date is associated with the control, the information should be provided by the Selection control pattern. |
Required UI Automation Events
The following table lists the UI Automation events required to be supported by all calendar controls. For more information about events, see UI Automation Events Overview.
UI Automation Event |
Support |
Notes |
|---|---|---|
Required |
None |
|
BoundingRectangleProperty property-changed event. |
Required |
None |
IsEnabledProperty property-changed event. |
Required |
None |
IsOffscreenProperty property-changed event. |
Required |
None |
Required |
None |
|
Required |
None |
|
CurrentViewProperty property-changed event. |
Depends |
None |
HorizontallyScrollableProperty property-changed event. |
Depends |
If the control supports the Scroll control pattern, it must support this event. |
HorizontalScrollPercentProperty property-changed event. |
Depends |
If the control supports the Scroll control pattern, it must support this event. |
HorizontalViewSizeProperty property-changed event. |
Depends |
If the control supports the Scroll control pattern, it must support this event. |
VerticalScrollPercentProperty property-changed event. |
Depends |
If the control supports the Scroll control pattern, it must support this event. |
VerticallyScrollableProperty property-changed event. |
Depends |
If the control supports the Scroll control pattern, it must support this event. |
VerticalViewSizeProperty property-changed event. |
Depends |
If the control supports the Scroll control pattern, it must support this event. |
Required |
None |