Thank you for the response. Working from your input, I now understood how
TabIndex properties nest with the nesting of components. (This is not at
all clear in the documentation.) So top level components must be numbered
0, 1, 2, etc. Then within those components, one starts renumbering again
from 0. So one might end up with, for example:
0.0, 0.1, 0.2, 1, 2.0, 2.1, 3, 4.0, 4.1, 5.0, 5.1, 5.1.1, 5.1.2, 5.2,
5.3
When the user tabs through a form, these numbers are simply consumed from
lowest to highest. Thus, since 4.1 is smaller than 5.0, the control at 4.1
will be reached before the one at 5.0.
On Tue, 11 Apr 2006 01:33:33 -0700, Linda Liu [MSFT]
<v-****@online.microsoft.com> wrote:
Hi Michael,
Thank you for posting. From your post, my understanding on this issue
is:
When you run your application and press the Tab key repeatedly, you can
not
get proper focus order on your form. If IĄŻm off base, feel free to let
me
know.
Since some controls such as Label TextBox are put into a Panel in your
project, the PanelĄŻs TabIndex property should be set properly first. For
example, there are four Panels on your form and each Panel contains
several
controls. To get proper focus order, the four PanelsĄŻ TabIndex
properties
should be set to sequent numbers and the TabIndex properties of the
controls in one Panel should be set to sequent numbers too.
Please let me know if you have any other concerns, or need anything
else.
Sincerely,
Linda Liu
Microsoft Online Community Support
================================================== ==
When responding to posts,please "Reply to Group" via
your newsreader so that others may learn and benefit
from your issue.
================================================== ==
