لطفا منتظر باشید ...
Child Windows
Each window is connected via a parent/child relationship scheme. Applications create a main window with no parent, called a top-level window. That window might (or might not) contain windows, called child windows. A child window is clipped to its parent. That is, no part of a child window is visible beyond the edge of its parent. Child windows are automatically destroyed when their parent windows are destroyed. Also, when a parent window moves, its child windows move with it.Child windows are programmatically identical to top-level windows. You use the CreateWindow or CreateWindowEx function to create them, each has a window procedure that handles the same messages as its top-level window, and each can, in turn, contain its own child windows. To create a child window, use the WS_CHILD window style in the dwStyle parameter of CreateWindow or CreateWindowEx. In addition, the hMenu parameter, unused in top-level Windows CE windows, passes an ID value that you can use to reference the window.Under Windows CE, there's one other major difference between top-level windows and child windows. The Windows CE shell sends WM_HIBERNATE messages only to top-level windows that have the WS_OVERLAPPED and WS_VISIBLE styles. (Window visibility in this case has nothing to do with what a user sees. A window can be "visible" to the system and still not be seen by the user if other windows are above it in the Z-order.) This means that child windows and most dialog boxes aren't sent WM_HIBERNATE messages. Top-level windows must either manually send a WM_HIBERNATE message to their child windows as necessary or perform all the necessary tasks themselves to reduce the application's memory footprint. On Windows CE systems that use the standard "Explorer shell," which supports application buttons on the taskbar, the rules for determining the target of WM_HIBERNATE messages are also used to determine what windows get buttons on the taskbar.In addition to the parent/child relationship, windows also have an owner/owned relationship. Owned windows aren't clipped to their owners. However, they always appear "above" (in Z-order) the window that owns them. If the owner window is minimized, all windows it owns are hidden. Likewise, if a window is destroyed, all windows it owns are destroyed.
