Here's the situation. The UltraSpellChecker is working great for me EXCEPT when there is a huge note with a lot of mis-spellings. My client reports that it is slowing their new Win 10 machines down to a crawl, when they enter the note screen, and makes typing almost impossible. It is slow for me on my machine, but not quite as bad as theirs. It's actually the nature of the text data - a lot of codes, FEIN numbers, ID's, names, etc., that show up as mis-spelled even though they are correct. This particular note I am looking at is about 100 lines, with an average of 3 or 4 "bad" words per line.
Now here's the problem. I know how to fix this in future releases - I can make the program spell check on demand only. But my client is a huge corporation, and it takes an act of God to get out new releases (and God is slow, so that means no more than one program update per year).
After that set up, finally to my question:
Is there any way I can disable spell check for them on their current version of the program (i.e., without changing code)? I was hoping there would be an INI file setting, or a file I could add or delete that would prevent any spellcheck activity.
My program is VB.NET, with a RichTextBox, which has a property of SpellCheckerSettings on UltraSpellChecker.Enabled=True.
Thanks!
Hello Ted,
Thank you for your post!
Unfortunately, there does not exist a way to essentially “shut off” the UltraSpellChecker and prevent it from spell-checking outside of doing it through code.
I find it interesting that the UltraSpellChecker is creating such a performance impact in this case, though. Would it be possible for you to please provide a sample that demonstrates this performance issue that you are seeing so I may investigate it further on my end?
Please let me know if you have any other questions or concerns on this matter.
Also, they have a 32 bit version of the program running on 64 bit Windows. Not sure if that is relevant. Mine is 64 bit and is still a little slow on a very fast machine.
Hi Andrew,
I sent data by email, hope you received it.
1. The slowness is apparent when the form is loaded. The RTF control property SpellCheckerSettings.Enabled = True. So when the form is loaded spellchecking was being performed automatically. This was slow. I have since made spellcheck on entry to screens an option, and now the form loads quickly, but no spellcheck until they do this (on demand):
SpellCheckerSettings.Enabled = True UltraSpellChecker1.ShowDialogsModal = True UltraSpellChecker1.ShowSpellCheckDialog(CType(frm.ActiveControl, TextBoxBase))And then it is slow to do the spell check and also slow when typing, i.e., the keyboard buffer can';t keep up, and I am typing faster than it can show on the screen because of the background spellcheck going on I presume. Note that I believe this only happens when there are hundreds of mis-spellings (in our example they are not actually mis-spelled words, they are codes).
2. Infragistics4.Win.UltraWinSpellChecker.v19.1.20191.150
Thank you for sending the data – I have received it.
Upon testing the UltraSpellChecker with your data on button click, I am able to see some performance issues in this case. The main issues I am seeing are as follows:
1. Upon click of the button and running the code you have provided, I am able to see that the spell check takes around 5 seconds to complete.
2. In the dialog, after using one of the options, it appears that the spell check needs to re-evaluate for the entire document, which takes a few seconds.
3. After closing the dialog, the scrolling of the RichTextBox is very slow.
These behaviors appear to be unexpected, and as such, I have asked our engineering staff to examine this further. To ensure it receives attention, I have logged this behavior in our internal tracking systems with a development ID of 268983. I have also created a private support case for you, which I will be linking to this internal issue so that you can be notified of a fix or other resolution to it. This support case has an ID of CAS-206597-Z1Q2B1 and you can access it here.
Great, thank you!
An idea; maybe you can exclude any words that have numbers or non-alpha codes in them from the spell check.
I'm pretty sure the SpellChecker already does this by default. There are a whole bunch of properties to control this under ultraSpellChecker.SpellOptions including a property called AllowWordsWithDigits which defaults to false.I'm not sure that helps performance, though. In fact, it might even hurt performance, since it means the SpellChecker has to check every letter in every word to see if it contains digits in order to know whether to exclude it. Or presumably check each letter in the word until it hits a digit, which may or may not be near the beginning or the end of the word.