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.

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?

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.

You are correct.

I verified that it is not the Toolbar that is intercepting Ctrl+A.
I also commented out the 2 'Key' handlers I had added and the problem remains.

The only thing left that might be intercepting Ctrl+A is the UltraFormManager.
I dont have an events attached to that - I use it only to apply a style - but maybe it has some intrinsic handling of Ctrl+A. Aparently that tells it to do something that is not valid - that would explain the 'beep' when I press Ctrl+A.

I don't see anything about shortcuts in the documentation ... but then there is virtuslly no info on this class except for the list of properties and methods.

Does UltraFormManager intercept Ctrl+A? and if so how do I prevent it from doing so?

mikedempsey said:

Does UltraFormManager intercept Ctrl+A?

I can't think of any reason why it would do so.

You said that other controls on the same form don't respond to Ctrl+A, either. Is that right? Is it just Infragistics controls or does the same thing happen with a TextBox control?

Assuming it's all controls, then there must be something on that form eating the keystroke before it gets to them. Seems unlikely that it's the FormManager. but again, this should be very easy to test - just take it off and see if the problem goes away.

Other things that could be eating the keystroke are a ContextMenu, inbox ToolStrip/MenuStrip, or the KeyPreview event of the form. I suppose you could also try disabling or removing the toolbar on the main form just to further rule it out.

You are correct. It is not the UltraFormManager.

I removed the FormManager and the one key handler I had on one of the dialogs and I still get the beep when pressing Ctrl+A.
The dialog does not have a context menu or any inbox controls, and I don't use KeyPreview.
The only context menus are the ones built into your controls. [and for the text editor that includes a working 'Select All' menu.]

Since I only care about Select All for the text boxes and those only exist on 2 dialogs I will simply add KeyDown handlers to those 3 text boxes. That solves the issue even if I can't track down the root cause.