Hi,
When my app first starts, I am able usually to Tab among the panes in our main window (which uses RadDocking) and their children just fine.
However, after performing a drag rearrangement of the panes if I press Tab it does not work.
Tab also fails if we create a few other top-level windows then activate our main window (which has the docking panes).
I used Spy++ and a utility I created to monitor which Win32 hwnd has focus. I see that for both cases, focus is left in the large transparent window which hosts all the floating panes, compasses and visual cues.
A workaround is simply to click in the window again but it's confounding to our power users who use the keyboard a lot.
Does anyone have any ideas how we could avoid this? In my admittedly-limited experience, that transparent window sure seems to be a trouble-maker as there are other problems it causes as well.
John
When my app first starts, I am able usually to Tab among the panes in our main window (which uses RadDocking) and their children just fine.
However, after performing a drag rearrangement of the panes if I press Tab it does not work.
Tab also fails if we create a few other top-level windows then activate our main window (which has the docking panes).
I used Spy++ and a utility I created to monitor which Win32 hwnd has focus. I see that for both cases, focus is left in the large transparent window which hosts all the floating panes, compasses and visual cues.
A workaround is simply to click in the window again but it's confounding to our power users who use the keyboard a lot.
Does anyone have any ideas how we could avoid this? In my admittedly-limited experience, that transparent window sure seems to be a trouble-maker as there are other problems it causes as well.
John