ASPxSchedulerListEditor Class
Represents the Scheduling List Editor used in the XAF ASP.NET Web Forms applications.
Namespace: DevExpress.ExpressApp.Scheduler.Web
Assembly: DevExpress.ExpressApp.Scheduler.Web.v23.2.dll
NuGet Package: DevExpress.ExpressApp.Scheduler.Web
Declaration
public class ASPxSchedulerListEditor :
SchedulerListEditorBase,
ITestable,
ISupportModelSaving,
ISupportInplaceEditRemarks
List Editors are used by List Views to display object collections in a UI. The ASPxSchedulerListEditor is implemented in the Scheduler module, and is designed to present and manage scheduling information:
To display object collections, the ASPxSchedulerControl is used as the underlying control. The ASPxSchedulerControl is a descendant of the ASPxScheduler class.
The ASPxSchedulerListEditor supports a range of features out of the box:
This List Editor has the View Navigator, used for quick movement one page back or forward, or to the current date:
Supplies the View Selector used to easily switch between different scheduling Views:
Has the Date Navigator, providing a quick and easy way of changing the dates in the scheduling area:
The Date Navigator can be accessed using the ASPxSchedulerListEditor.DateNavigator property. The number of visible calendar rows can be specified using the IModelListViewSchedulerWeb.DateNavigatorRowCount property of the Application Model‘s IModelListView node.
As a descendant of the SchedulerListEditorBase, the ASPxSchedulerListEditor implements the IControlOrderProvider interface - supports the RecordsNavigationController‘s PreviousObject and NextObject Actions:
- Supports Resources and Recurring Events.
The ASPxSchedulerListEditor is targeted for objects that implement the IEvent interface from the Business Class Library.
For a thorough explanation of how to work with the ASPxSchedulerListEditor, refer to the Scheduler Module topic.
Note
ASPxSchedulerListEditor supports only Client and DataView modes (CollectionSourceBase.DataAccessMode).
Tip
Due to the XAF core specificity, it is not allowed to create objects directly from a nested List View of a Many-to-Many related object. This limitation becomes significant for the Scheduler when you try to edit an occurrence of series through a Scheduler Control of a Resource (assuming the Resource Detail View is invoked through an Event Detail View and the occurrence was not previously edited). Information about an exception from a recurrent event is stored in a separate IEvent object so a new object is created when you click the “Edit” menu item for the first time. The internal code of the SchedulerListEditor uses the NewObjectViewController.NewObjectAction to create a new object. This action is hidden from the UI in the circumstances described above.