Chapter Two Windows Programming and MFC Application Framework.pptVIP

C++ and Visualized Programming Chaper 6 Windows Programming and MFC Introducing Index 2.1 The Windows Programming Model 2.1.1 Message Processing 2.1.2 Handles 2.1.3 Windows APIs 2.1.4 A Windows Program 2.2 Introducing MFC 2.2.1 The Visual C++ Components 2.2.2 MFC Application Framework 2.1 The Windows Programming Model Programs written for traditional operating environments use a procedural programming model in which programs execute from top to bottom in an orderly fashion. The path taken from start to finish may vary with each invocation of the program depending on the input it receives or the conditions under which it is run, but the path remains fairly predictable. In a C program, execution begins with the first line in the function named main and ends when main returns. In between, main might call other functions and these functions might call even more functions, but ultimately it is the program—not the operating system—that determines what gets called and when. 2.1 The Windows Programming Model Windows programs operate differently. They use the event-driven programming model, in which applications respond to events by processing messages sent by the operating system. An event could be a keystroke, a mouse click, or a command for a window to repaint itself, among other things. 2.1 The Windows Programming Model 2.1.1 Message Processing Where do messages come from, and what kinds of information do they convey? Windows defines hundreds of different message types. Most messages have names that begin with the letters WM and an underscore, as in WM_CREATE and WM_PAINT. One way to characterize a Windows program is to think of it as a collection of message handlers. To a large extent, it is a programs unique way of responding to messages that gives it its personality. typedef struct tagMSG { HWND hwnd; UINT message; WPARAM wParam; LPARAM lParam; DWORD time; POINT pt; } MSG; 2.1.1 Message Processing 2.1.2 Hand