BUG: Can Click in Code Window Without Activating it in VB.EXE

Last reviewed: June 21, 1995
Article ID: Q74194
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

If you have both a form and code window present at design time in Microsoft Visual Basic with the current focus on the form, clicking the upper or lower edge of the splitter bar in the code window fails to shift the focus to the code window. Clicking anywhere else in the code window correctly shifts the focus and activates the code window.

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

To reproduce this problem in Visual Basic, choose the New Project option from Visual Basic's File menu. Double-click Form1 to open a code window, then click Form1 to return focus to the form. Now place the tip of the mouse pointer on the upper or lower edge of the code window's splitter bar such that the pointer remains an arrow, and is not an I-beam pointer or splitter pointer. Clicking now fails to shift the focus to the code window. You can click anywhere else in the code window and the code window will correctly become the active window.

Note that the "splitter bar" (the horizontal border just above the editing area and just above the vertical scroll bar) allows you to split the code window into two parts, which allows you to view two different sections of code at once.


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


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.