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:

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. 

Hi Mike,

That is a puzzle.

The only other thing I can think of to try would be to show the form on it's own, and not as a child of the parent form. Just show it using the Show method without passing in an owning window and see if that has any effect. If that works, then something on the parent form is eating the key stroke.

I tried that and it made no difference... so I guess it has to be somehow 'local' to the dialog.

However it applies to ALL my dialogs so it's something I'm doing as a standard.
The one possibly unusual thing I am doing is placing an UltraGroupBox onto the form to fill the client area and act as a 'backgroupd panel' for applying appearance settings.  I even removed that ... and it made no difference. 

I think I'll just have to accept that something odd is going on and use my workaround.

Hello Mike,

I am just checking about the progress of this issue. Let me know if you need my further assistance on this issue.

Thank you for using Infragistics Components.

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.

Hi Mike,

Thank you for the update.

When you have the time, please upload the sample. I will be glad to look into it.

I am looking forward to your reply.

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.