































Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Windows Styles, Hierarchy of windows, Desktop Window, Top level Window, Overlapped Window, Popup Window, Child window, Threads, Worker Thread, Client area, Edit Control Styles are the terms you can learn in this lecture and few others as well.
Typology: Slides
1 / 39
This page cannot be seen from the preview
Don't miss anything!
































The basic building block for displaying information in the Microsoft® Windows™ graphical environment is the window. Microsoft Windows manages how each window relates to all other windows in terms of visibility, ownership, and parent/child relationship. Windows uses this relationship information when creating, destroying, or displaying a window
When Windows initializes, it creates a window, known as the desktop window , that is sized to cover the entire display area and upon which all other windows are displayed. The window manager uses the desktop window as the top of the window manager's list. Thus, the desktop window is the top of the window hierarchy.
Another type of relationship can exist between top-level windows: Top-level windows can own or be owned by other top-level windows. An owned window is always above its owner in the Z order and is hidden when its owner is minimized
The desktop window occupies the first level of the windows hierarchy and top-level windows occupy the second level. Child windows , which are windows created with the WS_CHILD style, occupy all other levels. The window manager connects child windows to their parent window in the same way it connects top-level windows to the desktop window.
When owner window is minimized, owned
window is hidden.
Destroying owner window destroy sall
owned windows.
Owned windows are always displayed on
the top of their owner window.
A worker thread is commonly used to handle background tasks that the user shouldn’t have to wait for to continue using your application. Tasks such as recalculation and background printing are good examples of worker threads. This article details the steps necessary to create a worker thread.
In Windows, a thread that handles user input and responds to user events independently of threads executing other portions of the application. User-interface thread own one or more windows and have their own message queue. User- interface thread process messages received from the system.
A control is a child window an application uses in conjunction with another window to perform simple input and output (I/O) tasks. Controls are most often used within dialog boxes, but they can also be used in other windows. Controls within dialog boxes provide the user with the means to type text, choose options, and direct a dialog box to complete its action. Controls in other windows provide a variety of services, such as letting the user choose commands, view status, and view and edit text.