CWinApp follows similar design like a singleton class. A singleton class uses a static member to hold its own instance. Constructor is made private and thus objects cannot be created with new operator or in local space. singleton class saves its own object in that static member and it never creates more than one object. It creates first instance and returns the same object for the subsequent creations. Thus it represents only a single instance and shares the same instance to all the context of an application.
CWinApp also holds static private members to hold many application resources. It provides many global API calls like AfxGetApp, AfxGetInstanceHandle,AfxGetResourceHandle,AfxGetAppName etc to access singleton resources of an application. Any MFC apllication deals with only one application instance. However the design of CWinApp is not a pure singleton class. Constructor of CWinApp is not private and thus from development point of view there is no restriction to create multiple objects. In case of multiple application object declared in development , it takes the latest object pointer and it works with no problen. However it is recomended to create only one instance as the remaining objects will be unused. MFC has a sanity check and gives an assertion during runtime if we are running debug build.
About our authors: Team EQA
MFC hides WinMain in its framework and includes source file on WinMain(). This explains how framework calls global CWinApp::Initinstance() from entry WinMain.
This is constructed during global C++ objects are constructed and is already available when Windows calls the WinMain function, which is supplied by the ...
Define a custom Window class structure, Register the class name, CreateWindow, Show windows and write message get and dispatch loop statements. Define the Window CallBack procedure and write the handlers.
DispatchMessage() is a API which indirectly triggers the Window CallBack procedure. Message structure members from this function are passed to the CallBack procedure. CallBack procedure should implement event handlers depending on the need of the application.
LPARAM and WPARAM are the two parameters in Window CallBack procedure. They signifies parameters of various events. They are used in handing individual events.
We need to write WinMain and need to follow all these in a Win32 application. However we need not to write much if we are writing an application with MFC ...
Questions index C Questions C++ Questions Win32 MFC COM/DCOM DLL Questions
Compilers & Editors
Download Visual Studio Download XCode Download Visual Studio Code Android studio install sdk Eclipse installer Best C compilers IDEs
Development system setup
Windows media creation tool MSDN subscription Ubuntu virtualbox
New updated posts
Why learn C? Draw on printer Memory leaks