Spell Checking Application Fields

[mlmanfredi]

It seems the IgnoreAllFields and IgnoreReadOnlyFields properties in RapidSpellAsYouType do not affect ApplicationFields. Shouldn’t they since ApplicationField is derived from TextField?

Is there any way to keep it from spell checking ApplicationFields?

Thanks,
Mike

[Fabian Zenker]

Hi Mike!

I am not able to reproduce that issue. I my eyes the IgnoreAllFields and IgnoreReadOnlyFields properties in RapidSpellAsYouType work correct for ApplicationFields.

Could you please provide me a sample document or/and project that shows this issue? Which version do you use?

Regards,
Fabian

[mlmanfredi]

Fabian - Thanks for the reply. While putting together a sample, I discovered that if I set property before adding the field it appears to work. If the field has already been underlined by the spell checker, changing the property does not remove the underline.

So it looks more like a refreshing issue. I have tried doing a ForceCheckAll() and RepaintUnderlines() but neither results in the underlines being removed. How do I refresh the spell checking?

Also, I tried calling Refresh() on the text control but that caused all underlines to go away – even the lines that should have remained. They returned when I clicked on the document. This may be a separate issue but is it a known problem?

Thanks,
Mike

[Fabian Zenker]

Hi Mike!

It seems as if that behaviour is a bug. ReforceCheckAll() does not consider the changes you've set at rapidSpellAsYouType1.IgnoreAllFields.

You can workaround that issue by resetting the TextControl to the SpellChecker:

            
rapidSpellAsYouType1.IgnoreAllFields =!rapidSpellAsYouType1.IgnoreAllFields;
rapidSpellAsYouType1.TextControl = null;
rapidSpellAsYouType1.TextControl = textControl1;

Regards,
Fabian

[mlmanfredi]

Seems to work well. Thank you.

[Fabian Zenker]

Hi Mike!
Your issue will be fixed in TX Text Control RapidSpell .NET 15.1 Service Pack 1. We will release it on the Second of March 2010.
Regards,
Fabian

[lehua768]

Fabian - Thanks for the reply. While putting together a sample, I discovered that if I set property before adding the field it appears to work. If the field has already been underlined by the spell checker, changing the property does not remove the underline.