FIX: TabStop Property Does Not Work
ID: Q180846
|
The information in this article applies to:
-
Microsoft Windows CE Toolkit for Visual Basic 5.0, version 1.0
SYMPTOMS
Setting the TabStop property of a control to False has no affect.
RESOLUTION
Use one of the following workarounds:
- Use the LostFocus event of the control preceding the control to be
skipped in the Tab order. In the LostFocus event procedure, set the
focus to the next control in the desired Tab order.
In the following example, there are three CommandButtons in Tab order
Sequence (Command1, Command2, and Command3); it is suggested that you
skip Command2:
Private Sub Command1_LostFocus()
Command3.SetFocus 'skip Command2
End Sub
NOTE: If Command1 opens a form, dialog, or other item that receives
the focus, this will not work.
- Add a dummy control, such as a CommandButton, and set its size to be
very small to effectively hide it. (The Visible property must remain
"True.") Set the TabIndex property to ensure it precedes the control to
be skipped in the Tab order. Add code to its GotFocus event procedure to
send the focus to desired control.
STATUS
Microsoft has confirmed this to be a problem in the Microsoft products listed
at the beginning of this article.
This problem was corrected in Windows CE Toolkit for Visual Basic 6.0.
MORE INFORMATION
Steps to Reproduce Behavior
- Create a new Windows CE Project in Visual Basic 5.0. Form1 is created
by default.
- Add three CommandButtons to Form1.
- Set the second CommandButton's TabStop property to False.
- Press the F5 key to run the project.
Pressing the TAB key will tab the focus from one button to the other,
but the second CommandButton should not get the focus because its
TabStop property is set to False.
REFERENCES
Online Books for Microsoft Windows CE Toolkit for Visual Basic version 5.0
Additional query words:
vbce vbce5 vbce6
Keywords : kbToolkit kbVBp kbVBp500bug kbVBp600fix kbWinCE kbWinCE100 kbGrpVB
Version : WINDOWS:1.0
Platform : WINDOWS
Issue type : kbbug
Last Reviewed: February 25, 1999