UserLookAndFeel.UseDefaultLookAndFeel Property
Gets or sets whether the current object’s settings are in effect.
Namespace: DevExpress.LookAndFeel
Assembly: DevExpress.Utils.v22.1.dll
NuGet Packages: DevExpress.Utils, DevExpress.Wpf.Core
Declaration
[DefaultValue(true)]
[DXCategory("Appearance")]
public virtual bool UseDefaultLookAndFeel { get; set; }Property Value
| Type | Default | Description |
|---|---|---|
| Boolean | true | true to use look and feel settings provided by the parent object or default look and feel object; false to enable this object’s settings. |
Remarks
If the UseDefaultLookAndFeel property is set to true and the UserLookAndFeel.ParentLookAndFeel property specifies a non-null value, look and feel settings are specified by the object assigned to the UserLookAndFeel.ParentLookAndFeel property.
If the UseDefaultLookAndFeel property value is true, but the UserLookAndFeel.ParentLookAndFeel property value is null (Nothing in Visual Basic), look and feel settings are controlled by an object available via the static UserLookAndFeel.Default property. This default look and feel can be customized at design time using the DefaultLookAndFeel component.
If the UseDefaultLookAndFeel property value is false, the UserLookAndFeel.SkinName property specifies the actual look and feel. You can disable this setting for an individual control to apply a unique skin to this control (if you choose to apply a vector skin, it will use its default palette), but this approach is not recommended. Instead, use Appearance.BackColor and Appearance.ForeColor properties to highlight controls.
Related GitHub Examples
The following code snippet (auto-collected from DevExpress Examples) contains a reference to the UseDefaultLookAndFeel 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.