Is there any sample code and/or is it possible to use the XamRichTextEditor with the XamSpellChecker?
Hello Ryan,
Thanks for your post.
Here is a simple sample project of xamRichTextEditor with XamSpellChecker. The SpellChecker checks the Tag property of the xamRichTextEditor and after spelling is completed updates the document.
If you have any further questions on this matter please do not hesitate to let me know.
Sincerely,
Horen
Software Developer
Infragistics
This is too simple a solution since it will remove all formatting in the document even if I choose to ignore all.
I was hoping for something that would keep the formatting already established in the editor.
Do you have a more advanced example or is this something on the to-do list?
Thank you for your feedback.
I have been looking into it. It seems that this is a custom scenario which is not implemented out of the box.What I can suggest in order to be able to achieve your requirement and ensure that the formatting is kept is to iterate each TextNode.Text. I have created a more advanced example in which each TextNode is updated separately. The sample application is showing a custom approach that can be used as a guideline for implementing the functionality that you are looking for.
This is very close to what I need. However, the spellchecker is not updating the suggestion area correctly on each word.
Example (using 14.2) :
Sentence: I beez badd (works fine)
Sentence : I beez badd (works fine for beez, but when you hit ignore, the words switches to badd, but the suggestions are still for beez)
Not sure why using the multiple nodes is different than for the one node of (I beez badd). But something in the spellcheck doesn't like successive words calls.
I am just checking if my last reply was helpful for you.
If you require any further assistance please do not hesitate to ask.
I have modified the project using TextNodes as multiple SpellCheckTargets. The project is currently using 14.2.
Please find it attached.
Were you able to recreate the problem and understand what I was saying?
Do I need to upgrade from 14.2 to 15 in order to fix this?
Looking for some answers on this one still.