AppointmentDisplayOptions.EndTimeVisibility Property
Specifies whether the end time should be visible for the appointment.
Namespace: DevExpress.XtraScheduler
Assembly: DevExpress.XtraScheduler.v19.2.Core.dll
Declaration
[DefaultValue(AppointmentTimeVisibility.Auto)]
public virtual AppointmentTimeVisibility EndTimeVisibility { get; set; }
Property Value
Type | Default | Description |
---|---|---|
AppointmentTimeVisibility | **Auto** | An AppointmentTimeVisibility enumeration specifying whether the appointment end time should be displayed. |
Available values:
Name | Description |
---|---|
Auto | Whether the appointment time is shown or not is determined automatically according to the current scheduler view’s settings. |
Always | Appointment time is always shown. |
Never | Appointment time is never shown. |
Property Paths
You can access this nested property as listed below:
Remarks
When the EndTimeVisibility is set to AppointmentTimeVisibility.Auto, the appointment’s end time is not shown in the following scenarios:
- if the appointment is of the Appointment.AllDay type;
if the appointment lines up with the time cell border in the Day View, Work Week View or Full Week View.
In the Day-like views, the appointment duration is represented by its height. Thus if the appointment overlaps the time cell border, the end time is not displayed. For example, if the DayView.TimeScale is 30 min, then the end time values of 2:00 and 7:30 will not be displayed, while 2:01 and 7:40 - will be.
The end time visibility may be affected by the AppointmentDisplayOptions.SnapToCells property. Depending on its value, the appointment will appear the following way.
Property values | Result |
---|---|
EndTimeVisibility = Auto SnapToCellsMode = Auto | Disabled | Never | |
EndTimeVisibility =Auto SnapToCellsMode =Always |
Related GitHub Examples
The following code snippet (auto-collected from DevExpress Examples) contains a reference to the EndTimeVisibility property.
Note
The algorithm used to collect these code examples remains a work in progress. Accordingly, the links and snippets below may produce inaccurate results. If you encounter an issue with code examples below, please use the feedback form on this page to report the issue.