BUG: Pressing ESC or CTRL+BREAK Makes Mouse Pointer Disappear

 Last reviewed: June 21, 1995
Article ID: Q74409
The information in this article applies to:

- Standard and Professional Editions of Microsoft Visual Basic for 

  Windows, version 3.0
- Microsoft Visual Basic programming system for Windows, version 1.0

SYMPTOMS

In Microsoft Visual Basic, the mouse pointer fails to be displayed if you press ESC or CTRL+BREAK within the Code window. (The mouse pointer correctly reappears if you move the mouse.)

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

Steps to Reproduce Problem

  1. Start Visual Basic with a New Project.

  2. Double-click the form to bring up the Code window. Notice the I-beam mouse pointer within the Code window. If you place the mouse pointer outside of the Code window, you will see the I-beam change to an arrow.

  3. Place the mouse pointer back in the Code window to display the I-beam pointer. Press either the ESC key or the key combination CTRL+BREAK. The I-beam mouse pointer will temporarily disappear.

  4. The pointer will be redisplayed if you move the mouse.

Additional reference words: buglist1.00 buglist3.00 1.00 3.00
KBCategory: kbenv kbbuglist
KBSubcategory: EnvtRun

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: June 21, 1995
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.