Description:
I wish to create a custom editor component derived from one of your XtraEditors editor. I could not find the descriptions of the protected virtual methods in the help (the Reference section). Will you describe all the class members in the future?
Answer:
There are several reasons, why protected class members are not documented. The primary reason is that we don't have the resources to describe them all: there are thousands of such methods in our code. Other reasons are:
- Most of our customers purchase our components to save their time. It is assumed that the component's functionality is more than enough to create an advanced UI and a feature rich application. Thus there is no need to inherit our classes. We suspect that not many programmers create descendants from our classes.
- The source code is the best documentation a programmer can get. We provide the source code for our products. It is recommended to purchase the suites with full source code, if you are going to extend our controls hierarchy with your own classes. If you have purchased a suite without source code, you can upgrade it to a suite with source code in Client Center.
We understand that creating derived classes from a third-party vendor's components is not a trivial task. That is why we create samples with descendants from our classes. In our Knowledge Base you can find articles devoted to the creation of custom XtraEditors classes, custom views for the XtraGrid and XtraNavBar, and so on.
See Also:
How to rebuild assemblies from the source code
How to create a GridView descendant class and register it for design-time use
How to register a custom editor for use in the XtraGrid
Custom XtraNavBar view: XPExplorer view without expand/collapse buttons and with always expanded groups