Well, if you have another dialog displayed, without a toolbar, then I'm not sure what happens. But there's really no reason to guess - this is incredibly easy to test. Just put a breakpoint in the ToolClick event of the ToolbarsManager. If it's firing, then the toolbar is handling the keystroke.

But if we are showing a modal dialog surely the toolbar [on the parent form] should not be intercepting keystrokes that are destined for the child dialog.

(In the specic case I reported they were modeless dialogs so it might be more murky there, but the same thing is happening on my modal dialogs also.)

Am I missing something here?

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.

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.