FIX: VB Debug.Print in MouseMove Event Causes MouseMove Event (72679)
The information in this article applies to:
- Microsoft Visual Basic Standard Edition for Windows 1.0
This article was previously published under Q72679 SYMPTOMS
Debug.Print used within the MouseMove event procedure of a form or
control causes a MouseMove event. If the mouse cursor is located
within the form or control, an endless stream of output to the
Immediate Window will occur. This behavior occurs for a program run in
the Visual Basic development environment. An .EXE program does not
utilize the Immediate Window and the Debug object so this behavior
does not apply to a .EXE program. The problem does not occur if a
Print method is issued to any other form or control in the program.
STATUS
This is not a problem with Visual Basic, but rather the nature of the
Microsoft Windows operating environment. This problem does not occur in
Visual Basic version 2.0 or 3.0.
Modification Type: | Minor | Last Reviewed: | 1/9/2003 |
---|
Keywords: | kbbug KB72679 |
---|
|