The UltraComboEditor [in edit mode] supports Ctrl+C, Ctrl+V, Ctrl+X, Ctrl+Z but ignores Ctrl+A.
The default context menu however includes 'Select All' so I would expect it to support Ctrl+A.
Is this a bug or is there a good reason why it does not support that shortcut?
ThanksMike
Hi Mike,
Thank you for contacting Infragistics Developer Support.
The UltraComboEditor does support Ctrl+A. I tested it using v13.2.20132.2023 and this functionality works properly for me, pressing the Ctrl+A selects the whole text. Could you please let me know exactly which version of Infragistics you are using? I have attached my sample, please modify it so it reproduces your issue and I will be glad to research your issue further.
I am looking forward to your reply.
I am using the slightly older version 13.2.20132.1011, but your sample works with that version also.
I suspect that the problem is related to the fact that Ctrl+A is also defined as a shortcut for the application's Ultra toolbar.
Past experience has shown me that the toolbar sometimes grabs shortcuts that I was not expecting it to grab.On further examination I find that it is not only the combo box that exhibits this issue. All the other 'ultra' editors I use on my modal and modeless dialogs also ignore the Ctrl+A shortcut, even though their context menus 'Select All' items work.(They don't just ignore the shortcut - the app 'beeps' when I type it.)
Strangely, Ctrl+C and Ctrl+V work fine for all controls - and those are also assigned to the toolbar.
mikedempsey said:I suspect that the problem is related to the fact that Ctrl+A is also defined as a shortcut for the application's Ultra toolbar.
You suspicion is almost certainly correct. The Toolbar will handle the keystroke and thus it will never get to the control. I'm sure you will get the same behavior with any control, including the inbox TextBox control, as well.
If Ctrl+C and Ctrl+V work, then my guess is that your toolbar's ToolClick event is already handling those for the controls on the form.
Hello Mike,
I am just checking about the progress of this issue. Have you had the time to look into this. Let me know if you need my further assistance on this issue.
Thank you for using Infragistics Components.
Thank you for the update.
When you have the time, please upload the sample. I will be glad to look into it.
I created a simple test app but the problem does not occur.
I used an empty parent form and displayed one of the actual dialogs that fails, but it works fine when called from this empty parent.
So apparently it is caused by the parent form even though it still occurs when I don't pass the parent to the Show() or ShowDialog() method.
I don't have time to work on this at the moment but I may revisit it later.
I am just checking about the progress of this issue. Let me know if you need my further assistance on this issue.
Are you able to create a small sample project which reproduces the issue? We will be glad to research the sample and this way we can locate the issue a lot faster.