Text Control Error Navigator Launched
We launched the Text Control Error Navigator to search for error numbers returned by TX Text Control exceptions. Errors can filtered by error numbers and the associated modules.

Exception Classes
To handle errors and exceptions - expected or unexpected - TX Text Control implements a detailed exception handling with different exception classes that informs about the error number and specific details:
- Filter
Exception - Formula
Exception - License
Level Exception - Number
Format Exception - Text
Editor Exception
Some errors are summarized to error groups with similar reasons. In all cases, an error number is provided in the exception message text. The following code is causing an exception as we are trying to load an invalid RTF string:
try {
textControl1.Load("test", TXTextControl.StringStreamType.RichTextFormat);
}
catch (FilterException exc) {
Debug.WriteLine("Message: {0}, Reason: {1}", exc.Message, exc.Reason.ToString());
}
Message: Text filter error: The file type is not supported through the filter.
(1-1D01), Reason: WrongFileType
In this case, the error description is very clear, but in other cases, the error number itself can provide some more details about the reason for the caused error.
Error Navigator
For these purposes, we launched the Text Control Error Navigator that can be used to search for error numbers in various modules. The interface is very simple:
It is possible to filter by error number and module. Let's search for the error number from our forced exception above (search for the second part after the dash):
Web API Search
To help you to integrate the error search into your own development environment and CI/CD pipelines, we provide a Web API for this search as well. The following endpoints are available:
https://errors.textcontrol.com/api/errors?number=2c&module=TextControl
[
{
"number":"1D01",
"description":"Filter error: the text data to be imported has the wrong text format.",
"module":"TextControl"
}
]
https://errors.textcontrol.com/api/errors/modules
[
{
"module":"FormatChecking"
},
{
"module":"GraphicsImportFilter"
},
{
"module":"ImageModule"
},
{
"module":"OleObjects"
},
{
"module":"TextControl"
}
]
Test this error navigator on your own:
Related Posts
MailMerge: Working with Image Placeholders
The MailMerge class is able to merge form fields, merge fields and objects such as barcodes or images. This article shows how to use image placeholders and how to insert them programmatically.
Restoring the Merge Field Default Behavior
The online document editor provides a default merge field behavior including a specific highlight color, a doubled input position and a highlight mode. When loading an Office Open XML (DOCX)…
New JavaScript API Calls for Typical MailMerge Tasks
This article shows how to use the improved JavaScript API for typical MailMerge tasks such as inserting merge blocks.
Add JavaScript to PDFs with TX Text Control in C# .NET: Time-Based Alerts…
In this article, we explore how to enrich PDF documents with JavaScript using TX Text Control in C# .NET. Read on to learn how to create time-based alerts that trigger actions based on specific…
Use MailMerge in .NET on Linux to Generate Pixel-Perfect PDFs from DOCX…
This article explores how to use the TX Text Control MailMerge feature in .NET applications on Linux to generate pixel-perfect PDFs from DOCX templates. This powerful combination enables…