Quote:
WPTools has a WPSpell which I thought was separate from and different than Addict's wpaddict.pas.
Yes, you're right about this. Julian also sells his own spelling checker built specifically for WPTools, but both our spelling checker and his own integrate into WPTools in a very similar manner.
It sounds, however, as though most of your problems are in dealing with configuration issues...
Quote:
For instance, I understand that except in unussual circumstances, more unussual than I am experienced to design, only one compenent should be on a form for the addict speller and addict thesuarus: either addictxxx or addictbasexxx,; thesaurusxxx or thesaurusbasexxx.
You should have only a single Addict Spell component and a single Addict Thesaurus component in your application. If they are only utilized on a single form, the recommended position is on that form. If they are utilized on multiple forms, the recommendation is to place the components on a shared data module that is created before the form. If you're using any of our UI or menuing then you do not want to use the base versions, but only the normal versions. The base versions really only existed in V3 for use by someone wanting the spelling engine for a completely custom solution. Most people do not need them.
Quote:
#1) The base sets are subsets of the other component, right?
All functionality in the base component is available in the full component.
Quote:
#2) having multiples of one, or one each of the super set and subset would amoung other things create multiple ConfigFileName properties with unpredictable or potentially complicated (and undesired) behavior.
Correct. You do not want to do this as you'll have two completely different instances of configuration "fighting" one another.
Quote:
The problem we are having is this... When we add a speciallized dictionary to the active dictionaries through the dialogs by checking its check box, we get exactly the behavior we want: additional words are recognized as found (correctly spelled.)
The problem is that when we leave the program and rerun, we need to re-add the check mark to the checkbox. We need to have BOTH the ability to CHECK this box for the user's initial use, and KEEP it checked for future use, without messing up the rest of the usability.
If I were to guess your problem here, I'd probably guess one of the following:
* You're using multiple instances of the spelling component (or a normal and a base component) all in the same application. This effectively leaves the configuration in a last-writer-wins situation where the configuration that wasn't changed can overwrite the one that was.
* Your application is leaking the Addict spelling component (it's never being freed). As mentioned in your other thread, by default the configuration is saved on component shutdown...
* The configuration is setup in such a manner that it fails to write -- unreachable filename, etc...
This should be a good starting point for you to examine...
Thanks,
Michael Novak
Addictive Software