-
Apr 17th, 2018, 01:20 PM
#1
Ink Edit Spell Checking
When Spell Check is enabled on an Ink Edit box,
http://www.vbforums.com/showthread.p...ows-SpellCheck
any text already in the box is not checked for spelling. Your program must refresh the text in order for spell checking to be applied. That is the case for Windows 8.1.
However, Windows 10 does not behave the same way. When text is programatically added to the box, spell checking is not applied. One work around is to cut and paste the text, and then spell checking is applied. But this is a pain in the butt.
Does anyone know how Win 10 can be made to behave the same way as Win 8.1?
J.A. Coutts
-
Apr 17th, 2018, 02:04 PM
#2
Re: Ink Edit Spell Checking
As far as I can tell the newer RichEdit controls (which InkEdit wraps) were never meant to spellcheck programmatic text at all. The are supposed to check typed or handwritten text. Pasted text may be intentionally checked as well.
Sounds like a bug fix, so it is unlikely it will change back.
Your usage sounds a little bizarre. If you wanted to programmatically check spelling your could use the API yourself: Spell Checking API.
-
Apr 17th, 2018, 05:37 PM
#3
Re: Ink Edit Spell Checking
I am only using it as a bonus for using the Ink Edit control. I have no interest in developing code to enable it's use. Spell checking was introduced with Windows 8, and I find it strange that MS would reduce it's functionality for Windows 10. It must have something to do with features introduced with Win 10.
I used to use the MS Word spell checker in my email client, but when you brought it to our attention, I quickly converted it to an Ink Edit control, and it is much simpler and easier to use. On Win 8.1, it spell checks inbound email as well as outbound mail. But on Win 10, it only spell checks outbound email.
J.A. Coutts
-
Apr 17th, 2018, 10:37 PM
#4
Re: Ink Edit Spell Checking
RichEdit has gained new features since Windows 8.1, so perhaps in implementing them they "broke" something that worked before but was not in the specifications? Or for all we know this change may have been made on purpose in response to a bug report.
Windows 8.1 is now in Extended Support which diminishes the odds of any change to bring it into compliance.
Whether this change is a bug or a fix can only be determined by Microsoft. You could always try filing a support incident, and your case would be bolstered if you can point out where the previous behavior was documented.
Otherwise you merely got burned by relying on a quirk.
-
Apr 18th, 2018, 11:35 AM
#5
Re: Ink Edit Spell Checking
Ya, I'm coming to the same conclusion. Detailed technical information on this feature is in extremely short supply. It looks like we are stuck with the work around. I did notice that the Spelling feature under settings/devices/typing must be enabled for Spell Check to work at all.
J.A. Coutts
-
Apr 18th, 2018, 12:53 PM
#6
Re: Ink Edit Spell Checking
I agree. As far as RichEdit goes the documentation at MSDN was never updated to cover these newer features at all as far as I can tell. Everything past RichEdit 4.1 that I know about I found discussed in Microsoft blogs but really nowhere else.
This is probably less nefarious than it is negligent. All of their energies seem to be on Azure, .Net, and WinRT, their biggest fails. Everything else gets little but minimal custodial attention unless the Office team wants it.
Windows itself is turning into a sort of Mad Max dystopian landscape.
-
Apr 20th, 2018, 02:13 AM
#7
Re: Ink Edit Spell Checking
FYI, there is LCID member on CHARFORMAT2 that is probably used by spell-checking functionality.
A single RichEdit control can have a text with two paragraphs in different languages so spelling has to somehow know which dictionary to use for each of these ranges.
Could be a problem in the Ax Control converting design-time StdFont::Charset to CHARFORMAT2::lcid
cheers,
</wqw>
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|