INFO: Overlapping Controls Are Not Supported by Windows

ID: Q79981

The information in this article applies to:

SUMMARY

Child window controls should not be overlapped in applications for the Windows operating system. When one control overlaps another control, or another child window, the borders shared by the controls may not be drawn properly. Overlapping controls may confuse the user of the application because clicking the mouse in the common area may not activate the control that the user intended to activate. This behavior is a consequence of the way that Windows is designed.


MORE INFORMATION

The following example illustrates the painting problems caused by the ambiguity of overlapping borders. Consider three edit controls, called A, B and C, which overlap each other, and an enclosing child window D: 


     ____________________________________________
     | | A          | B          | C          | |
     | ---------------------------------------- |
     |                 D                        |
     --------------------------------------------

Assume that control B has the focus. If this set of controls is covered by another window, which is subsequently moved away, Windows will send a series of client and nonclient messages to each of the controls and to the enclosing child window. The result of these messages may appear as the illustration below, where the portion of window B's border that overlapped with part of window D's border is missing: 

     _______________             ________________
     | | A          | B          | C          | |
     | ---------------------------------------- |
     |                 D                        |
     --------------------------------------------

Repainting problems related to overlapping controls may vary depending on the version of Windows used. 


Keywords          : kbCtrl kbDlg kbNTOS kbGrpUser kbWinOS kbWndw kbWndwProp 
Version           : 
Platform          : 
Issue type        : kbinfo

Last Reviewed: March 7, 1999