For example, it is useful to have access to the Clear and Add buttons of the ASPxLookupDropDownEdit, which is used in the ASPxLookupPropertyEditor.
See Also:
How to hide New button on ASPxLookupPropertyEditor
Anatol
We have closed this ticket because another page addresses its subject:
Usability - Make it possible to hide Clear Action via the application model
Hello,
The ASPxLookupDropDownEdit class also already provides the DropDown property, allowing you to access its underlying ASPxComboBox. Accessing this property is required to accomplish numerous customizations of ASPxLookupPropertyEditor:
http://search.devexpress.com/?q=DropDown+ASPxLookupPropertyEditor&p=T4%7cP2%7c54&d=2
We do not provide public properties that would allow you to directly access the New and Clear buttons themselves, because we are not aware of useful scenarios with them. The only useful scenario we are aware of is the scenario when it is necessary to hide the New or Clear buttons to prevent the creation/clearing objects via the lookup. The ASPxLookupDropDownEdit class, which is used along with ASPxLookupFindEdit in various display modes of ASPxLookPropertyEditor, already provides the AddingEnabled and ClearingEnabled properties for that. This property can be set in code as shown at How to hide New button on ASPxLookupPropertyEditor.
In addition, you can do the same thing without even writing even a single line of code. Just invoke Model Editor, and then navigate to a required LookupListView for the class of your lookup property.
After that, set its AllowNew property to False. That's it.
The above functionality is already available in current XAF versions, and so I am closing the current suggestion.
If you experience other useful scenarios where it is helpful to directly access underlying properties of PropertyEditors, just let us know. We will be glad to review your cases and improve our products, if required.
Thanks,
Dennis