BUG: SizeGrip of Status Bar Paints Incorrectly in Windows NT

 Last reviewed: April 26, 1996
Article ID: Q150203
The information in this article applies to:
  • Standard, Professional, and Enterprise Editions of Microsoft Visual Basic, 32-bit only, for Windows, version 4.0

SYMPTOMS

If a status bar is placed on a form in Microsoft Visual Basic, and if the height of the status bar is made larger than the height of the SizeGrip, the SizeGrip incorrectly paints in the upper-right corner of the status bar when it should stay in the lower corner of the bar.

This only applies when running under WINDOWS NT 3.5x.

STATUS

Microsoft has confirmed this to be an issue in the Microsoft products listed at the beginning of this article. Microsoft is researching this issue and will post new information here in the Microsoft Knowledge Base as it becomes available.

WORKAROUND

There is no workaround to this problem other than avoiding it by keeping the status bar the same height as the SizeGrip.

Steps to Reproduce Problem

  1. Start a new project in Microsoft Visual Basic. Form1 is created by default.

  2. Draw a Statusbar on the form and make it very high.

Notice that the SizeGrip is painted in the upper right hand corner of the bar. This behavior does not change when the project is run.

Additional reference words: 4.00 3.5x vb4win vb432
KBCategory: kbprg kbusage
KBSubcategory: PrgCtrls



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: April 26, 1996
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.