All docs
V21.2
21.2
21.1
20.2
20.1
The page you are viewing does not exist in version 20.1. This link will take you to the root page.
19.2
The page you are viewing does not exist in version 19.2. This link will take you to the root page.
19.1
The page you are viewing does not exist in version 19.1. This link will take you to the root page.
18.2
The page you are viewing does not exist in version 18.2. This link will take you to the root page.
18.1
The page you are viewing does not exist in version 18.1. This link will take you to the root page.
17.2
The page you are viewing does not exist in version 17.2. This link will take you to the root page.

CompatibilitySettings.UseLegacyQueryIntervalCalculation Property

Specifies whether to calculate QueryStart and QueryEnd individually for each SchedulerControl‘s occurrence.

Namespace: DevExpress.Xpf.Core

Assembly: DevExpress.Data.Desktop.v21.2.dll

Declaration

public static bool UseLegacyQueryIntervalCalculation { get; set; }

Property Value

Type Description
Boolean

true, to calculate QueryStart and QueryEnd individually for each occurrence; false, to use the pattern’s QueryStart and QueryEnd for changed and deleted occurrences.

Remarks

In v20.1 and earlier, QueryStart and QueryEnd for modified and deleted occurrences were calculated individually, and returned values different from the QueryStart and QueryEnd of their pattern. In certain scenarios, this prevents such occurrences from being correctly loaded (see: T923353). You can set the UseLegacyQueryIntervalCalculation property to true to revert to this behavior.

In v20.2 and later, QueryStart and QueryEnd for changed and deleted occurrences return the same values as the pattern’s QueryStart and QueryEnd.

Starting with v20.2, the Scheduler implements the FetchAppointments / FetchTimeRegions events. These events allow you to load scheduler items for the visible date interval on demand. When you use this feature to load recurrent patterns for the requested interval, you need to load all changed and deleted occurrences as well.

Important

If you set UseLegacyQueryIntervalCalculation property to true, the FetchAppointments / FetchTimeRegions events stop working correctly.

See Also