xtrareports-devexpress-dot-xtrareports-dot-userdesigner-dot-xrdesignmdicontrollerdesignsettings-2ed39c52.md
This property is no longer used.
Indicates whether to use a legacy Filter Editor or a new one in reporting applications.
Namespace : DevExpress.XtraReports.UserDesigner
Assembly : DevExpress.XtraReports.v25.2.Extensions.dll
NuGet Package : DevExpress.Win.Reporting
[Browsable(false)]
[Obsolete("This property is no longer used.", false)]
public DefaultBoolean UseLegacyFilterEditor { get; set; }
<Obsolete("This property is no longer used.", False)>
<Browsable(False)>
Public Property UseLegacyFilterEditor As DefaultBoolean
| Type | Description |
|---|---|
| DefaultBoolean |
true if a legacy Filter Editor is used. By default, this property is set to false.
|
Available values:
| Name | Description | Return Value |
|---|---|---|
| True |
The value is true.
|
0
| | False |
The value is false.
|
1
| | Default |
The value is specified by a global option or a higher-level object.
|
2
|
You can access this nested property as listed below:
| Object Type | Path to UseLegacyFilterEditor |
|---|---|
| XRDesignMdiController |
.DesignSettings .UseLegacyFilterEditor
|
A Filter Editor allows you to construct filter criteria in a tree-like form using the Visual mode or manually using the Text mode. The primary difference between the legacy Filter Editor and the new one is the Text mode implementation.
The Legacy Filter Editor has two tabs for constructing filter criteria.
The new Filter Editor has a single-tab interface.
In addition, the new Filter editor has an enhanced text criteria builder. It supports intelligent code completion (suggesting functions and available data fields as you type) and error validation.
By default, the new Filter Editor is used in reporting applications. You can keep using the legacy Filter Editor by setting the UseLegacyFilterEditor property to true.
See Also
XRDesignMdiControllerDesignSettings Class