Unregistered
January 14, 2003, 04:45:29
Support,
Well you certainly did better than I did with ComponentOne's Spell.net and TX!
There are still problems with it, though. All of them are resolvable, in time.
Problems:
1. There is currently no way to have the Spell Dialog to position itself so that the user can see what is being marked. Users would object if the dlg didn't position itself away from the pertinent text.
2. It may be the .net TX Find function needs looking at. Your line:
FindSuccess = TextControl1.Find(C1Spell.CheckWord, NewPos, TXTextControl1.FindOptions.NoMessageBox)
is not starting at the NewPos, but actually starts at the top of the text. To test type this into a document:
mre
smething
mre
smething
mre
smething
Run spell check. Ignore the first mre. Ignore the first smething. Change all the second mre. All MRE's are now changed in the control, but not in the text Spell is working on, so the highlight on the next misspelled word is wrong, taking white space. Thus, I think the tx FIND has a problem in the start position.
3. I'll address this directly with ComponentOne: The suggestions given are horrible, and incorrect. Look at the suggestions you get for thi, for example: "chi, ihi, phi, tai, tchi, th, tha, thio, thir, tho, ti, toi, tshi, tui, twi"!!!! Our users would SCREAM at us if we let that pass as valid suggestions! ComponentOne needs to improve the suggestions, degree difference, before we could possible use it. And ComponentOne needs a non-GUI interface for those of us what want to do our own interface. (Perhaps a word from you guys asking them about it would go a LONG way in convincing them! My previous email to them about this went unanswered.)
4. We've got time to get all the bugs worked out, but this evening I spent hours searching for other viable options for a speller engine. RapidSpell looks good, and PolarSoftware has something, and there's Spellex. I don't know if Polar and Spellex are in dot net yet, but have written them to inquire. My first choice is ComponentOne, if they are willing to address user needs.
This message was originally posted by Vann Joe in the old TX Text Control Support Forum.
Well you certainly did better than I did with ComponentOne's Spell.net and TX!
There are still problems with it, though. All of them are resolvable, in time.
Problems:
1. There is currently no way to have the Spell Dialog to position itself so that the user can see what is being marked. Users would object if the dlg didn't position itself away from the pertinent text.
2. It may be the .net TX Find function needs looking at. Your line:
FindSuccess = TextControl1.Find(C1Spell.CheckWord, NewPos, TXTextControl1.FindOptions.NoMessageBox)
is not starting at the NewPos, but actually starts at the top of the text. To test type this into a document:
mre
smething
mre
smething
mre
smething
Run spell check. Ignore the first mre. Ignore the first smething. Change all the second mre. All MRE's are now changed in the control, but not in the text Spell is working on, so the highlight on the next misspelled word is wrong, taking white space. Thus, I think the tx FIND has a problem in the start position.
3. I'll address this directly with ComponentOne: The suggestions given are horrible, and incorrect. Look at the suggestions you get for thi, for example: "chi, ihi, phi, tai, tchi, th, tha, thio, thir, tho, ti, toi, tshi, tui, twi"!!!! Our users would SCREAM at us if we let that pass as valid suggestions! ComponentOne needs to improve the suggestions, degree difference, before we could possible use it. And ComponentOne needs a non-GUI interface for those of us what want to do our own interface. (Perhaps a word from you guys asking them about it would go a LONG way in convincing them! My previous email to them about this went unanswered.)
4. We've got time to get all the bugs worked out, but this evening I spent hours searching for other viable options for a speller engine. RapidSpell looks good, and PolarSoftware has something, and there's Spellex. I don't know if Polar and Spellex are in dot net yet, but have written them to inquire. My first choice is ComponentOne, if they are willing to address user needs.
This message was originally posted by Vann Joe in the old TX Text Control Support Forum.