Intersoft Community - WebTextEditor - Using SpellChecker, with context menu and a standard ASP Text Box

Using SpellChecker, with context menu and a standard ASP Text Box

yudi — Mon, 15 Nov 2010 03:30:54 GMT

I’d like inform you about the status of work item #792.

WebGrid development team has managed to get the issue resolved in WebGrid 7. I have tested the nightly build of the hotfix and found that the issue no longer persists.

Should you need to have the nightly build hotfix to be tested on your local end, please let us know.

Using SpellChecker, with context menu and a standard ASP Text Box

yudi — Tue, 14 Sep 2010 18:00:19 GMT

Thank you for the feedback regarding the nightly-build of the hotfix.
I have forwarded this to the development team to be fixed.

Using SpellChecker, with context menu and a standard ASP Text Box

mdgardipee — Tue, 14 Sep 2010 08:51:59 GMT

Good news related to this fix. The following has been resolved with the latest build:

Any misspelled word followed by one of the following is now underlined, and working correctly:

Period
Comma
Semi Colon

There are still some open issues however.

Any misspelled word followed by any of the following is NOT underlined as misspelled

Colon
Parenthesis

Any misspelled word PRECEDED by any of the following is NOT underlined as misspelled.

Period
Semi Colon
Colon
Comma
Parenthesis

So, we're getting closer but it's not complete. I appreciate that prompt response as our release candidate can not go to our clients until these issues are resolved.

Thanks,

Michael Gardipee

Using SpellChecker, with context menu and a standard ASP Text Box

yudi — Mon, 13 Sep 2010 15:49:30 GMT

I’d like to inform you that WebTextEditor development team has managed to fix the issue (as submitted under work item #792). I also have ensure that the issue no longer persist using the nightly-build hotfix of WebTextEditor 1. I’ve uploaded the nightly-build hotfix to be tested on your end. Please let us know whether the nightly-build hotfix helps or not.

Please download the nightly-build hotfix of WebTextEditor at here.

Note

*The nightly-build hotfix has not been extensively tested (disclaimer on). So, we are really appreciate if you have encountered an issue can kindly give us a feedback of it.

*Please carefully follow the step-by-step shown in this link, in order to apply the hotfix manually.

*Please close all opened Microsoft Visual Studio opened project during applying the hotfix.

*After finish apply the hotfix to your development machine, please don’t forget to apply this hotfix to your own project.

*It is recommended to do ‘iisreset’; clear ‘Temporary ASP.NET Files’ in “C:\Windows\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files” folder; and clear browser’s cache before re-test the issue using the hotfix.

Using SpellChecker, with context menu and a standard ASP Text Box

mdgardipee — Mon, 13 Sep 2010 14:12:34 GMT

So it sounded like you have a fix for the punctuation that preceded or follows misspelled words. Is that something I can get and test out? Time is short for us so either we have to document that this is a known issue in our help system, or get it fixed.

Thanks,

Michael Gardipee

Using SpellChecker, with context menu and a standard ASP Text Box

handy@intersoftpt.com — Wed, 08 Sep 2010 17:23:09 GMT

Hello,

I have been forwarded your replied regarding my last post.

I uninstalled the RC and installed R1, and have the same problem. This isn’t earth shattering for us as I alluded to in my postings, just that it exists and I am wondering if it is the tag structure that is throwing you off.

Would you mind to let us know about your environment details. We still could not replicate in here.
About your QA result, I will need to discuss with our developer teams about this issue.

Regards,
Handy

Using SpellChecker, with context menu and a standard ASP Text Box

mdgardipee — Wed, 08 Sep 2010 11:25:16 GMT

Darn - I forgot (1) character. The same will happen with a parenthesis, either open or closed. Here is the actual note from our defect tracking system as posted by one of our QA members.

When a misspelled word is preceded by a Period, Comma, Semi Colon or Parenthesis, the misspelled word is not identified by Spell Checker. I will create a defect to track this issue, but is this something that will be getting fixed?

　　　　　　　　 Verify that a misspelled word proceeded by punctuation is identified:

　　　　　　　　 Verify that a misspelled word proceeded by punctuation is identified:

　　　　　　　　 Period - DEFECT

　　　　　　　　 Period - DEFECT

　　　　　　　　 Comma - DEFECT

　　　　　　　　 Comma - DEFECT

　　　　　　　　 Semi colon : - DEFECT

　　　　　　　　 Semi colon : - DEFECT

　　　　　　　　 Colon : - DEFECT

　　　　　　　　 Colon : - DEFECT

　　　　　　　　 Parenthesis " - DEFECT

　　　　　　　　 Parenthesis " - DEFECT

　　　　　　　　 Apostrophe ‘–PASS 4.5.5.4

　　　　　　　　 Apostrophe ‘–PASS 4.5.5.4

　　　　　　　　 Left/Right () Bracket –PASS 4.5.5.4

　　　　　　　　 Left/Right () Bracket –PASS 4.5.5.4

Using SpellChecker, with context menu and a standard ASP Text Box

mdgardipee — Wed, 08 Sep 2010 11:17:44 GMT

Actually, our QA group has found that any word that is either preceded by or followed by the following (4) characters will cause the spell checker to miss words that are misspelled.

Semi Colon (;)

Colon (:)

Period (.)

Comma (,)

Thanks,

Michael Gardipee

Using SpellChecker, with context menu and a standard ASP Text Box

handy@intersoftpt.com — Mon, 06 Sep 2010 15:42:46 GMT

Please do not click on autoreply. It seems you posted into "Intersoft Community Notification services".
However, I received your last post via email (forwarded from development division).

I already followed your step by step but still unable to replicate this issue.
It seems this error only showed in RC installer.
To get the latest assemblies, I suggest you to uninstall the RC and installed the release version.
http://www.intersoftpt.com/Community/ClientUI/Updated-WebUI-Studio-2010-Installer-Is-Now-Available/.
Hope this helps.

Regards,
Handy

Using SpellChecker, with context menu and a standard ASP Text Box

yudi — Mon, 06 Sep 2010 00:04:48 GMT

About the first issue, since you said that it is reproduce-able using the local-live sample, could you please kindly let us know the detail of step-by-step to replicate the issue?

I just got news from the WebSpellChecker development team that the issue related to the added period sign will cancel the spell check has been solved. I’m going to test the nightly-build of the hotfix before I send it to you. I’ll keep you updated with the test result.

Using SpellChecker, with context menu and a standard ASP Text Box

mdgardipee — Wed, 01 Sep 2010 15:27:56 GMT

I have implemented two solutions for integrating the spell checker into an application, one that uses an ASP Text Box and consequently (it seems) the Spell Checker dialog and the other with an IFrame that will only underline the misspelled words with the red line. I prefer the red underline for ease of use, plus there are a few bugs in the Spell Checker dialog that is keeping me from using that until Intersoft addresses them.

So, with that said, has someone implemented the Spell Checker, with the Context menu and NOT the dialog and pointed it to an ASP Text Box as opposed to an IFrame? Any samples or guidance would be appreciated.

Thanks,

Michael Gardipee