Log In
Home
Support
Demos
Documentation
Blogs
Training
Webinars
[Expand]General Information
[Collapse]WinForms Controls
  Prerequisites
 [Expand]What's Installed
 [Expand]Build an Application
 [Collapse]Controls and Libraries
  [Expand]Forms and User Controls
  [Expand]Messages, Notifications and Dialogs
  [Collapse]Editors and Simple Controls
   [Collapse]Simple Editors
    [Expand]Included Components
    [Collapse]Editors Structure
      Editor Hierarchy
      Editor Class Structure
      Editor Containers
      Repositories and Repository Items
      Custom Editors
    [Expand]Editors Features
    [Expand]Member Tables
    [Expand]Examples
   [Expand]Lookup Editors
   [Expand]Token Edit Control
   [Expand]Breadcrumb Edit Control
   [Expand]Range Control
   [Expand]Image Slider
    Camera Control
  [Expand]Ribbon, Bars and Menu
  [Expand]Application UI Manager
  [Expand]Docking Library
  [Expand]Data Grid
  [Expand]Vertical Grid
  [Expand]Pivot Grid
  [Expand]Tree List
  [Expand]Chart Control
  [Expand]Diagrams
  [Expand]Gauges
  [Expand]Map Control
  [Expand]Scheduler
  [Expand]Spreadsheet
  [Expand]Rich Text Editor
  [Expand]Spell Checker
  [Expand]Form Layout Managers
  [Expand]Navigation Controls
  [Expand]Printing-Exporting
  [Expand]PDF Viewer
   Reporting
  [Expand]Snap
  [Expand]TreeMap Control
 [Expand]Common Features
  Get More Help
 [Expand]API Reference
[Expand]ASP.NET Controls and MVC Extensions
[Expand]ASP.NET Bootstrap Controls
[Expand]WPF Controls
[Expand]Xamarin Controls
[Expand]Windows 10 App Controls
[Expand]Document Server
[Expand]Reporting
[Expand]Report Server
[Expand]Dashboard
[Expand]eXpressApp Framework
[Expand]CodeRush
[Expand]Cross-Platform Core Libraries
[Expand]Tools and Utilities
 End-User Documentation

Editor Hierarchy

This topic describes the class structure of the editors available for in-place editing in container controls or as standalone controls. All of these editors are derived from the abstract BaseEdit class. Note that this class does not implement any editor-specific functionality for editor painting, responding to user actions, etc. So, if you need to create a custom editor class that has no features in common with any existing editor, you should derive your editor from the BaseEdit class.

Editors derived from the BaseEdit class can be divided into logical groups with respect to their immediate parent. For example, the BaseSpinEdit class is the immediate parent of the SpinEdit and TimeEdit editors. It implements the functionality required to edit values using spin buttons. It is derived from the ButtonEdit class, which enables buttons to be used within editors. The ButtonEdit class is a descendant of the TextEdit class, which enables a box to be displayed for editing text. As you can see, each group of controls has common functionality provided by ancestor classes. Each ancestor brings its own functionality, so that editor functionality is increased as you go down the inheritance tree. This tree is displayed in the image below. Key classes (base classes introducing new functionality used by several editors) are displayed on the left. Their immediate descendants (editors that belong to the same logical editor group) are displayed on the right.

 

 

The list below provides a brief description of each editor group:

How would you rate this topic?​​​​​​​