Log In
[Expand]General Information
[Collapse]WinForms Controls
 [Expand]What's Installed
 [Expand]Build an Application
 [Collapse]Controls and Libraries
  [Expand]Forms and User Controls
  [Expand]Messages, Notifications and Dialogs
  [Expand]Editors and Simple Controls
  [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]Map Control
  [Collapse]Rich Text Editor
   [Expand]Getting Started
     Supported Document Formats
     Layout API
     Product Class Structure
     Default Keyboard Shortcuts
     Measure Units
     HTML Tag Interpretation
   [Expand]Visual Elements
   [Expand]Member Tables
  [Expand]Spell Checker
  [Expand]Form Layout Managers
  [Expand]Navigation Controls
  [Expand]PDF Viewer
  [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]Report Server
[Expand]eXpressApp Framework
[Expand]Cross-Platform Core Libraries
[Expand]Tools and Utilities
 End-User Documentation


The RichEditControl control implements the main Rich Edit functionality and is available on the DX.17.1: Rich Text Editor toolbox tab in Visual Studio IDE.

RichEditControl is the "plain" rich editor, without a toolbar or extra panels. In the MS Visual Studio Designer, it looks as shown below.

You can create Ribbon or bar UI for XtraRichEdit, as described in the How to: Create a Simple Word Processor with a Ribbon UI and How to: Create a Simple Word Processor with a Bar UI articles.

A visual control RichEditControl and its non-visual counterpart, the RichEditDocumentServer, are the main entities that implement the Rich Editor functionality. They are built upon the same core object, the inner RichEdit Document Server, so you are free to choose one that suits your application needs.

The functionality of the inner RichEdit Document Server is programmatically accessible via the native API. The Document interface exposed via the IRichEditDocumentServer.Document or the RichEditControl.Document property is the main way for a programmer to use API methods and properties. The native API is located in the DevExpress.XtraRichEdit.API.Native namespace.

The RichEditControl displays a document via a set of Views. When a document is loaded, the Document Model is constructed, and is transformed into the Document Layout. The current RichEditControl.ActiveView renders and displays the layout. Therefore, a document exists only in its native RichEdit representation. To get a document or a part of a document in any other format, a corresponding exporter is utilized.

The class diagram below can help you understand types and relations.

For more information on the document structure and on the interaction between a model and a layout, refer to the Document article.

For an overview of RichEditControl events, review the Events article.

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