C1SpellChecker TextBox DataBinding Issue

Posted by: james on 14 July 2022, 3:17 pm EST

  • Posted 14 July 2022, 3:17 pm EST - Updated 3 October 2022, 1:22 pm EST

    There is an issue with the right click context menu item “Spelling”.

    This issue does not effect the selection of a spelling suggestion.

    In other words, the issue effects the button I have highlighted in Red. The option highlighted in green works all good.

    The issue is only if the TextBox is bound to a BindingSource.

    If you click the “Spelling” button, all changes made to the textbox since load disappear straight away. In other words, the difference between what was bound, and what is currently in the textbox.

    Here are pictures to explain what I mean.

    To mitigate the problem I listen to the TextBox MouseDown event and call BindingSource.EndEdit(), but I do not like this solution as it is prone to error down the track when I use the Spelling Control on another bound text box.

    This does not happen if the TextBox is not bound.

    Is this a known issue?

    Also, is there a way to override the “Spelling” button on the context menu to call CheckControl with “false” for FromCursor instead of true? Because even if the user right clicks on a word at the start of the TextBox and uses that button it will not show the dialog at all if the cursor is currently at the end of the textbox.

  • Posted 17 July 2022, 7:47 pm EST

    Hi,

    We have reported the issue to the development team and will let you know as soon as we have an update. [Tracking Id : C1WIN-27749]

    To change the behavior of the “Spelling” context menu item, you can use the ContextMenuCreated event. In the event handler, you can remove the original toolstripitem and add a similar toolstripitem. Then you can handle the click event of the new item to perform your custom function. Please refer to the sample attached that calls the CheckControl method with fromCursor = false.

    Regards

    Avnish

    SpellCheck_Custom.zip

  • Posted 19 July 2022, 4:36 pm EST

    that’s great. thank you for the sample.

  • Posted 7 April 2024, 5:19 pm EST

    any updates regarding [Tracking Id : C1WIN-27749]

    Thanks

  • Posted 9 April 2024, 2:36 pm EST

    Hello,

    The development team is currently working on this issue. Unfortunately, we do not have a concrete ETA for the fix yet, but we will let you know as soon as we get an update from them.

    Thank you for your patience and cooperation.

    Regards,

    Uttkarsh.

  • Posted 10 April 2024, 11:40 am EST

    Hi Uttkarsh

    Thanks for the reply. It has been nearly 2 years. I found a workaround for the issue as mentioned above, but was wondering how long bugs (with available workarounds like the one above) take to resolve. As mentioned, the workaround is manual, and needs to be repeated whenever the control is used.

    Kind Regards

    James

  • Posted 10 April 2024, 10:21 pm EST

    Hello James,

    We completely understand your concerns regarding the delay in the issue fix and apologize for the inconvenience caused to you. Developers have provided a tentative ETA of 2024v1 Hotfix 1. Rest assured, our developers are actively working on it and will try to fix it as soon as possible.

    In the meantime, if you encounter any further challenges or have any questions, please don’t hesitate to reach out. We’re here to assist you.

    Thank you for your patience and understanding.

    Regards,

    Uttkarsh

  • Posted 11 April 2024, 12:00 pm EST

    Hi Uttkarsh

    Thanks.

    Kind Regards

    James

Need extra support?

Upgrade your support plan and get personal unlimited phone support with our customer engagement team

Learn More

Forum Channels