alt keys in mdi windows form application

[Craig Cody]

Has anyone seen the situation where you open multiple child forms within an
MDI application ... child forms that have alt hot keys defined. Invoking an
alt hot key that is defined on more than one child form will put the cursor
on the associated control of the first child form opened and not on the
associated control of the active form. The active form remains active. If
you start typing, the data is actually keyed into the associated control on
the first child form opened without that form being active. If the child
forms are stacked on top of each other, it appears that you've lost the
cursor or that you're locked up when in reality you are typing into a
control on a form that you can see unless you navigate to that form and make
it active. This behavior seems to have entered into our application upon
migrating to the 1.1 framework. We've replicated this behavior in a demo
application. What's the work around?

(e-mail address removed)

 

[Craig Cody]

Actually, the alt-key combination doesn't go back necessarily to the first
child form, but instead got to the next child form in the parents array of
child forms. Invoking the alt-key combination enough times will cause
eventually cycle around to the original active child form.

 

[Craig Cody]

It seems as though we found the solution. A Google newsgroups search did
provide a workaround:


http://groups.google.com/groups?hl=...eEnOzwdDHA.2320%40TK2MSFTNGP12.phx.gbl&rnum=2


Alternative link: http://tinyurl.com/uq1m