WinApp: Navigate TabPage using custom keys

[Mecena]

Hi!

I'm using arrow keys to navigate thru controls and I want my tab control to
implement that feature too, so when tabpage gets entered (focus is on the
header) DOWN key should focus on first tabpage control. Now, how can it
be achieved? I used to navigate using my utility classes, but recently
discovered that SendKeys.Send(" {TAB}") works fine too on most controls. Can
I use it on tab too?

thnx,
M.

[Shashi Sadasivan]

Hi!

I'm using arrow keys to navigate thru controls and I want my tab control to
implement that feature too, so when tabpage gets entered (focus is on the
header) DOWN key should focus on first tabpage control. Now, how can it
be achieved? I used to navigate using my utility classes, but recently
discovered that SendKeys.Send(" {TAB}") works fine too on most controls. Can
I use it on tab too?

thnx,
M.

Hi,
Glad to see someone in the same mess as me. (using custom navigation keys)
Well...If you use the {TAB} with the tabControl focused, it will go onto the next control (which will obviously not be the next tab page)
Tab pages are scrolled using the arrow keys (left and right) so you would have to send the arrow keys, but then someone has to make the decesion on which keys will those be, or commit to selecting tab pages using the mouse.

However, you could create chortcut keys (Alt+1 for tabpage1, and so on). This may be easier

I convinced them to use the mouse for tab selection , So i havent had the need to implement that as yet.

[Mecena]

:) Hi!
Selecting tabpages is not the issue, selecting controls is. If my focus is on the tabpage header, {TAB} gives me the first control, which is fine. But when i focus on the first control, things get messy because i'm handling the tabcontrol's KeyDown which i cannot use since i'm handling KeyDown in my controls already. So what i need is some kind of a check to see if the tabpage header is actually focused, not the whole tabpage. Or some other idea?
M.

Hi,
Glad to see someone in the same mess as me. (using custom navigation keys)
Well...If you use the {TAB} with the tabControl focused, it will go onto the next control (which will obviously not be the next tab page)
Tab pages are scrolled using the arrow keys (left and right) so you would have to send the arrow keys, but then someone has to make the decesion on which keys will those be, or commit to selecting tab pages using the mouse.

However, you could create chortcut keys (Alt+1 for tabpage1, and so on). This may be easier

I convinced them to use the mouse for tab selection , So i havent had the need to implement that as yet.

[Shashi Sadasivan]

:) Hi!
Selecting tabpages is not the issue, selecting controls is. If my focus is on the tabpage header, {TAB} gives me the first control, which is fine. But when i focus on the first control, things get messy because i'm handling the tabcontrol's KeyDown which i cannot use since i'm handling KeyDown in my controls already. So what i need is some kind of a check to see if the tabpage header is actually focused, not the whole tabpage. Or some other idea?
M.

I thought you answered yourself there.
You need to check if the tabcontrol is selected n the tabcontrols keydown event

So in the tabControls keydown event check if the tabcontrol is focused, if yes then continue, else dont handle the keys

[Mecena]

wow. I thought I tried that one, but obviously haven't:) thanx, that was an eye opener right there:)

I thought you answered yourself there.
You need to check if the tabcontrol is selected n the tabcontrols keydown event

So in the tabControls keydown event check if the tabcontrol is focused, if yes then continue, else dont handle the keys