Depending on the implementation of the Submit functionality, you could create a command that invokes the desired functionality of RadSpellChecker. The control itself, however, cannot be directly invoked through XAML. When the users submit the form, you could use the AllAtOnce spellchecking mode
and verify that the text is correct. In case there are still errors, you can show a popup and one of the spell check dialogs (using the Check()
method) to the user so they can correct what is left. The actions of the user are not stored anywhere, though, and you can detect only if the spell checking has been canceled using the arguments of the SpellCheckingCompleted
event of RadSpellChecker or if a word has been added or removed from the dictionary in use using the DataChanged
event of DocumentSpellChecker
IControlSpellChecker controlSpellchecker = ControlSpellCheckersManager.GetControlSpellChecker(
DocumentSpellChecker documentSpellChecker = (DocumentSpellChecker) controlSpellchecker.SpellChecker;
documentSpellChecker.DataChanged += DocumentSpellChecker_DataChanged;
You are right that the OK button cannot be dismissed. I created a public item
which you can use to vote for extending the functionalities of RadSpellChecker. One of the improvements logged there is to allow loading custom dialogs for the control, which would allow you to customize the behavior of the dialog as well.
Hope this information is helpful.
Want to extend the target reach of your WPF applications, leveraging iOS, Android, and UWP? Try UI for Xamarin
, a suite of polished and feature-rich components for the Xamarin framework, which allow
you to write beautiful native mobile apps using a single shared C# codebase.