TX Text Control: Using TX Spell .NET with multiple TX Text Control instances

TX Spell .NET is the perfect addition for TX Text Control to add professional, high-performance and reliable spell checking to your applications. TX Spell .NET enjoys a deep integration within the main word processing component. Integrating TX Spell .NET for Windows Forms into TX Text Control requires no code - it can be easily connected using the Visual Studio designer. To increase performance, the spelling dialog is opened by TX Text Control and not TX Spell .NET. The dialog that is opened by TX Text Control is pre-configured and can't be customized. Alternatively, you can call a fully customizable SpellCheckDialog from TX Spell .NET.

The source code is contained in the following directories:

Using TX Spell .NET with multiple TX Text Control instances

A high-performance spell checker requires a well-considered concept to work with multiple controls on a form in the same application. A single TX Spell .NET instance can be used with multiple instances of TextControl. It is not necessary to have one instance of the spell checker, for each instance of TextControl. This dramatically reduces the required memory and speeds up the spell checking process.

The concept of using multiple instance of TextControl with the same instance of TX Spell .NET is very straightforward. It is not neccessary to switch manually between the controls. Different from other spell checker components, the connection between the consuming control and TX Spell .NET is set with TextControl. To connect TX Spell .NET with the TextControl, the SpellChecker property of each TextControl must be connected to the same TX Spell .NET instance.

After starting the application, each connected TextControl uses the same TX Spell .NET instance and therefore the same resources, dictionaries and user dictionaries.