Yep. I went that route. ProcessDialogKey() wasn't even being called. Come to find out I needed to derive from ContainerControl instead of Control to get the behavior. Never did figure out exactly the difference between Control and ContainerControl that fixed it.
> >It would seem that your control is somehow eating the key messages before it >passes them to it's parent. I would recommend handling Shift + Tab in your >control (by implementing ProcessDialogKey) and verifying that you are >receiving the (Shift + Tab) key messages. > >I know this isn't a real answer, but this is what I would try first when >debugging it. With a little more information (perhaps a sample project >displaying the problem) I could help more. > You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
