FIX: Control Overlaid by 2nd Control Won't Refresh If Moved (74519)
The information in this article applies to:
- Microsoft Visual Basic Standard Edition for Windows 1.0
This article was previously published under Q74519 SYMPTOMS
Visual 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.
WORKAROUND
This 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.
STATUS
This 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.
Modification Type: | Minor | Last Reviewed: | 1/9/2003 |
---|
Keywords: | kbbug KB74519 |
---|
|