SchedulerViewBase.GroupType Property
Gets or sets the type of grouping applied to the View.
Namespace: DevExpress.Xpf.Scheduler
Assembly: DevExpress.Xpf.Scheduler.v24.2.dll
NuGet Package: DevExpress.Wpf.Scheduler
Declaration
Property Value
| Type | Description |
|---|---|
| SchedulerGroupType | A SchedulerGroupType enumeration value that specifies how appointments are grouped within the View. |
Available values:
| Name | Description |
|---|---|
| None | No grouping is applied. |
| Date | Grouping by dates. Appointments are grouped by dates. |
| Resource | Grouping by resources. Appointments are grouped by resources. |
Remarks
Important
You are viewing documentation for the legacy WPF Scheduler control. If you’re starting a new project, we strongly recommend that you use a new control declared in the DevExpress.Xpf.Scheduling namespace. If you decide to upgrade an existing project in order to switch to the updated scheduler control, see the Migration Guidelines document.
If the View displays appointments which belong to more than one resource, then the GroupType property can be used to group the appointments within the View in a specific manner. The available types of grouping are specified by the SchedulerGroupType enumeration, and include grouping by dates, grouping by resources or no grouping. Grouping appointments by dates or resources facilitates the task of managing user time within the scheduling area.
Note that grouping can also be applied at the level of the SchedulerControl, via its SchedulerControl.GroupType property. When setting the SchedulerControl.GroupType property, its value is assigned to each View’s GroupType property, so that the same grouping will be applied within the scheduling area, regardless of the type of the scheduler’s active View (SchedulerControl.ActiveView). But the manner in which each particular view is grouped can be changed via the View’s GroupType property, that overrides the scheduler’s SchedulerControl.GroupType property.
Note
Do not use the GroupType property in the XAML markup. Instead use it in the code-behind file after calling the InitializeComponent method.