Microsoft KB Archive/171512: Difference between revisions
(importing KB archive) |
m (Text replacement - """ to """) |
||
Line 83: | Line 83: | ||
<li><p>Add the following code to the UserControl's code window:</p> | <li><p>Add the following code to the UserControl's code window:</p> | ||
<pre class="codesample"> Private Sub Command1_GotFocus() | <pre class="codesample"> Private Sub Command1_GotFocus() | ||
Debug.Print | Debug.Print "Command GF" | ||
End Sub | End Sub | ||
Private Sub Command1_LostFocus() | Private Sub Command1_LostFocus() | ||
Debug.Print | Debug.Print "Command LF" | ||
End Sub | End Sub | ||
Private Sub UserControl_EnterFocus() | Private Sub UserControl_EnterFocus() | ||
Debug.Print | Debug.Print "ENTERFOCUS" | ||
End Sub | End Sub | ||
Private Sub UserControl_ExitFocus() | Private Sub UserControl_ExitFocus() | ||
Debug.Print | Debug.Print "EXITFOCUS" | ||
End Sub | End Sub | ||
</pre></li> | </pre></li> | ||
Line 103: | Line 103: | ||
<li><p>Add the following code to the PropertyPage's code window:</p> | <li><p>Add the following code to the PropertyPage's code window:</p> | ||
<pre class="codesample"> Private Sub Command1_GotFocus() | <pre class="codesample"> Private Sub Command1_GotFocus() | ||
Debug.Print | Debug.Print "Command1 on property page GF" | ||
End Sub | End Sub | ||
Private Sub Command1_LostFocus() | Private Sub Command1_LostFocus() | ||
Debug.Print | Debug.Print "Command1 on property page LF" | ||
End Sub | End Sub | ||
</pre></li> | </pre></li> |
Latest revision as of 11:05, 21 July 2020
Article ID: 171512
Article Last Modified on 11/18/2003
APPLIES TO
- Microsoft Visual Basic 5.0 Control Creation Edition
- Microsoft Visual Basic 5.0 Professional Edition
- Microsoft Visual Basic 5.0 Enterprise Edition
This article was previously published under Q171512
SYMPTOMS
When using Property Pages that contain UserControls, code that is contained within the UserControls' Focus events (EnterFocus, ExitFocus, GotFocus, LostFocus) is not triggered.
STATUS
Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. This bug has been fixed in Visual Studio 97 Service Pack 2.
For more information on the Visual Studio 97 Service Pack 2, please see the following article in the Microsoft Knowledge Base:
170365 INFO: Visual Studio 97 Service Packs - What, Where, and Why
For a list of the Visual Basic 5.0 bugs that were fixed in the Visual Studio 97 Service Pack 2, please see the following article in the Microsoft Knowledge Base:
171554 INFO: Visual Basic 5.0 Fixes in Visual Studio 97 Service Pack 2
MORE INFORMATION
Steps to Reproduce Behavior
- Create a new Standard EXE project.
- Add a UserControl.
- Insert a CommandButton into the UserControl's designer.
Add the following code to the UserControl's code window:
Private Sub Command1_GotFocus() Debug.Print "Command GF" End Sub Private Sub Command1_LostFocus() Debug.Print "Command LF" End Sub Private Sub UserControl_EnterFocus() Debug.Print "ENTERFOCUS" End Sub Private Sub UserControl_ExitFocus() Debug.Print "EXITFOCUS" End Sub
- Add a PropertyPage to the project.
- Insert an instance of the UserControl onto the PropertyPage.
- Insert a CommandButton onto the PropertyPage.
Add the following code to the PropertyPage's code window:
Private Sub Command1_GotFocus() Debug.Print "Command1 on property page GF" End Sub Private Sub Command1_LostFocus() Debug.Print "Command1 on property page LF" End Sub
- In the UserControl's property browser, set the PropertyPage to PropertyPage1.
- Insert an instance of the UserControl on Form1.
- Right-click on the UserControl. Click Properties.
- Click on the CommandButton.
RESULT: NO EVENTS fire off, the Usercontrol's CommandButton should have gotten its LostFocus, the Usercontrol should have gotten its ExitFocus and the CommandButton should have gotten its GotFocus event.
REFERENCES
For more information on creating UserControls, please see Chapter 4 and 9 in the Component Tools Guide.
Keywords: kbbug kbfix kbvbp500sp2fix kbvs97sp2fix KB171512