.NET Framework 4.5.2+
.NET Framework 4.5.2+
.NET Standard 2.0+
.NET 5.0+

AppearanceAttribute.Enabled Property

Specifies whether to enable UI elements affected by the conditional appearance rule generated from this attribute instance.

Namespace: DevExpress.ExpressApp.ConditionalAppearance

Assembly: DevExpress.Persistent.Base.v21.2.dll

Declaration

public bool Enabled { get; set; }

Property Value

Type Description
Boolean

true, if UI elements affected by the conditional appearance rule must be enabled; otherwise, false.

Remarks

The following UI elements can be made disabled/enabled:

  • Data cells in a GridListEditor and ASPxGridListEditor when switching to the inline editing mode
  • Property Editors that are inherited from the PropertyEditor class.
  • Actions

You can find many examples in the Declare Conditional Appearance Rules in Code topic. See these examples in the Feature Center demo installed with the eXpressApp Framework in the %PUBLIC%\Documents\DevExpress Demos 21.2\Components\eXpressApp Framework\FeatureCenter folder, or refer to the Feature Center demo online.

The example below demonstrates how to disable the NickName property editor in the Contact Detail View.

using System;
using DevExpress.ExpressApp;
using DevExpress.ExpressApp.Actions;
using DevExpress.Persistent.Base;
using DevExpress.Persistent.BaseImpl;
// ...
public class Contact : Person, IMapsMarker {
// ...
    [Appearance("NickNameDisabled", Context = "Contact_DetailView", AppearanceItemType = "ViewItem", Enabled = false)]
    public string NickName {
        get {
            return nickName;
        }
        set {
            SetPropertyValue(nameof(NickName), ref nickName, value);
        }
    }
}

The following code snippets (auto-collected from DevExpress Examples) contain references to the Enabled 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.

See Also