Your Privacy Matters: We use our own and third-party cookies to improve your experience on our website. By continuing to use the website we understand that you accept their use. Cookie Policy
80
Keyboard Shortcuts for SpellCheckDialog?
posted

We are attempting to use the WinSpellChecker control to add spell checking to a WinForms application.  Our users are heavily keyboard-centric, and they have complained that the SpellCheckDialog does not have keyboard shortcuts.  I was surprised that when I hit the alt key on my keyboard, I did not see keyboard shortcuts on the SpellCheckDialog.  Is there a setting we are missing?  If not, is there any way to add our own keyboard shortcuts to the common commands on the dialog?

  • 71886
    Offline posted

    Hello acbush,

    What you could do is to handle the 'SpellCheckDialogOpening' event of the 'WinSpellChecker' control, cancel it and show your own dialog with the desired buttons with keyboard shortcuts.

     Please feel free to let me know if a question about our toolset comes up on your mind.

    • 71886
      Offline posted in reply to [Infragistics] Boris Toromanov

      Hello acbush,

      I wanted to know if you were able to solve your issue based on these suggestions or you still need help. Please let me know.

      • 71886
        Offline posted in reply to Andrew

        Hello,

        After some research, the "Support of shortcut keys in buttons in SpellCheckDialog" has been determined to be a new product idea. I have sent your idea directly to our product management team.

        Our product team chooses new ideas for development based on popular feedback from our customer base. Infragistics continues to monitor application development for all of our products, so as trends appear in requested features, we can plan accordingly.

        We value your input, and our philosophy is to enhance our toolset based on customer feedback. If your idea is chosen for development, you will be notified at that time.

        Your reference number for this product idea is PI12090075, for the xamSpellChecker is PI12090076.

        If you would like to follow up on your request at a later point, you may contact Developer Support management via email. Please include the reference number of your product idea in the subject and body of your email message. You can reach Developer Support management through the following email address: dsmanager@infragistics.com

        Thank you for your request.

        • 80
          posted in reply to [Infragistics] Boris Toromanov

          Thanks, Boris.  Yes please!  Could you log a similar request for the WPF xamSpellChecker, too?  I just looked at a sample for that control and noticed that it does not have keyboard shortcuts either.

          • 71886
            Verified Answer
            Offline posted in reply to Andrew

            Hello acbush,

            I believe that you have a very good point here. This should be implemented(shortcuts) in the dialog rather than creating a custom dialog and implementing all other logic just for this.

            So, do you want me to log a new product idea in our internal systems for this?

            • 80
              posted in reply to [Infragistics] Boris Toromanov

              Well, we are implementing our own spell check dialog, as per your suggestion, but it isn't a great solution.  Using the spell checker to iterate through the errors and apply corrections ourselves is not trivial.  When applying multiple corrections to an input string, it is difficult to keep track of the locations of errors.

              For example, let's say that the input string is "Helo my friendz and goodby."  The spell checker will identify errors at positions 0, 8, and 20 (if my counting is correct).  As we iterate through the errors, we want to build up a new string with the correct text, so after we apply the first correction, we have a new string "Hello my friendz and goodby."  Now, we want to apply the second correction to the string containing the first correction, not the original string.  Well, the errors collection tells us that the location of the second error is position 8, but relative to the string containing the first connection, the location of the second error how now shifted to position 9.  So this is difficult to keep track of.

              I am sure that Infragistics put a lot of work into solving these problems.  Input strings are probably tokenized, etc.  It would have been great to use this work rather than have to reimplement the logic just to have keyboard shortcuts.