RichEditDocumentServer.TrackedMovesConflict Event
Occurs when moved text has been changed since it was moved.
Namespace: DevExpress.XtraRichEdit
Assembly: DevExpress.RichEdit.v24.1.Core.dll
NuGet Packages: DevExpress.RichEdit.Core, DevExpress.Win.Navigation
Declaration
Event Data
The TrackedMovesConflict event's data class is TrackedMovesConflictEventArgs. The following properties provide information specific to this event:
| Property | Description |
|---|---|
| NewLocationRange | Provides access to the range of the moved text’s new location. |
| OriginalLocationRange | Retrieves the range of the moved text’s original location. |
| ResolveMode | Gets or sets what version of moved text to keep. |
| Revision | Provides access to the revision whose rejection fired the event. |
Remarks
When you move text, change it, and then reject this move, a conflict occurs that fires Document.TrackedMovesConflict and RichEditDocumentServer.TrackedMovesConflict events.
The event does not occur if new revision in the moved text was rejected.
You can obtain the original and new location range (OriginalLocationRange and NewLocationRange properties), and the revision that fired this event (the Revision property). Use the ResolveMode property to specify the version you want to keep.
The code sample below shows how to handle the TrackedMovesConflict event to keep original text:
private void WordProcessor_TrackedMovesConflict(object sender, TrackedMovesConflictEventArgs e)
{
//Compare the length of the original and new location ranges
//Keep text from the location whose range is the smallest
e.ResolveMode = (e.OriginalLocationRange.Length <= e.NewLocationRange.Length) ? TrackedMovesConflictResolveMode.KeepOriginalLocationText : TrackedMovesConflictResolveMode.KeepNewLocationText;
}
Related GitHub Examples
The following code snippet (auto-collected from DevExpress Examples) contains a reference to the TrackedMovesConflict event.
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.