FIX: Control Overlaid by 2nd Control Won't Refresh If MovedLast reviewed: October 30, 1997Article ID: Q74519 |
1.00
WINDOWS
kbenv kbbuglist
The information in this article applies to:
SYMPTOMSVisual Basic version 1.0 for Windows does not support overlapping controls. Having overlapping controls can result in portions of a control not refreshing correctly. If controls are moved over each other, then one or both of the controls may not correctly refresh even when the controls are moved apart. This is known to happen when controls are resized at run time using the Move method or by changing the Height and Width properties as a result of a Form_Resize event. Because controls must be resized one at a time, it is possible that one control will briefly overlap another control during the resize process at run time. The control that was briefly overlapped may not refresh properly. An example of this behavior is given in the More Information section below.
WORKAROUNDThis behavior can be improved by performing the Refresh method (CtrlName.Refresh) on every overlapping control at run time, after an overlapped control has been moved or after a form that contains overlapping controls has been resized.
STATUSThis is not a problem with Visual Basic. It is the nature of overlapping controls in Visual Basic version 1.0. This behavior occurs at run time in the Visual Basic development environment or as an .EXE program. This problem does not occur in Visual Basic version 2.0 or 3.0 for Windows where overlapping controls are supported.
MORE INFORMATIONFor more information about Visual Basic and overlapping controls, query in this knowledge base on the following words:
overlapping and controls and Visual and Basic Steps to Reproduce Problem
Picture1.Refresh VScroll1.Refresh Command1.Refresh |
Additional reference words: fixlist2.00 fixlist3.00 1.00 2.00 3.00
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |