Multiple Simultaneous Forms

[mlmanfredi]

In my app, I can have multiple text controls open at one time spanning multiple forms. What is the recommended way to handle spell checking in this situation? Should each form create its own spell checking components? Or should there be one set of spelling components maintained elsewhere - using AddTextComponent/RemoveTextComponent to dynamically include/exclude the text controls.

Also, I was wondering if you could explain the inconsistencies in the AddTextComponent and RemoveTextComponent. For RapidSpellAsYouType, there is an instance of each function that takes a TextControl argument. But RapidSpellDialog only supports TextControl in its add function and not the remove. Why? How do you remove a TextControl?

Thanks,
Mike

[Fabian Zenker]

Hi Mike!
Using the AddTextComponent is the best way to spellcheck multiple TextControls with one TX Text Control RapidSpell object:

Keyoti.RapidSpell.TX.RapidSpellAsYouType spellAsYouType = new Keyoti.RapidSpell.TX.RapidSpellAsYouType();
...
spellAsYouType.AddTextComponent(textControl1);
spellAsYouType.AddTextComponent(textControl2); 
...

The RemoveTextComponent issue was fixed in TX Text Control RapidSpell .NET version 15.1. Now there is also an overload for TextControl objects.

Regards,
Fabian

[mlmanfredi]

Hi Fabian. Thanks for the reply but it didn’t really answer my question. I am not asking how to spell check multiple text controls with a single rapid spell object. What I want to know is this: If I am opening and closing various forms with documents and sometimes have multiple open simultaneously, is it better to use a single rapid spell object or create one for each form? Thanks!

[Reallyethical]

That really depends on your application design.

If you are running a single thread then for memory optimization purposes having a single control is better, however if you are threading the application or creating in an MDI style, then having one per form is better.

This really has to be your decision.

Good Luck

Adam

[mlmanfredi]

Adam - Thanks for the info.

Fabian - I am using version 15.1 and I don't see the fix you mentioned. I see the following two RemoveTextComponent functions in the spell dialog and neither seems to be compatible with TextControl objects. Am I doing something wrong?

public virtual void RemoveTextComponent(ISpellCheckableTextComponent textComponent); // get run time error if cast to this interface
public virtual void RemoveTextComponent(TextBoxBase textBoxBase); // get compile error if cast to this type

Thanks,
Mike

[Fabian Zenker]

Sorry, it seems as if a TextControl components overload was implemented for the RemoveTextComonent method of the RapidSpellAsYouType component, but not for the RapidSpellDialog.

I will contact our partner Keyoti to fix this issue with the next service pack.

Fabian

[Björn Meyer]

I can confirm that this will be fixed within the next service pack for TX Text Control RapidSpell .NET.

Workarounds:

1. Provided that there is only one dictionary language being used (ie not changing language during runtime), call this before RapidSpellDialog.Check is called;

(rapidSpellDialog1.CheckerEngine as Keyoti.RapidSpell.RapidSpellChecker).ShareDictiona ry = true;

and then use one instance of RapidSpellDialog for every TextControl. Calling the above prevents each instance using a new copy of the dictionary.

[Fabian Zenker]

Hi!
We will release Service Pack on the Second of March 2010.
Regards,
Fabian