Win32 Application Steps
A standard Win32 windows program contains the following minimal steps:
- Define a Custom Window Class
- Define a WndProc() callback for this the window
- Register the Main Window Class
- Create the registered overlapped window
- Show and Update Window
- Wait for the user messages and dispatch to the window procedure
- Handle user required events in WndProc
MFC Application Steps
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 framework. This is the advantage of using MFC framework as MFC implements most of the steps inside its framework.
MFC is object oriented programming framework and most of the facilities are exposed as MFC classes. CWinApp is the class to take care WinMain and application initialization and running. Top level window display and management are done via CFrameWnd and CWnd classes.
MFC application should inherit CWinApp class and implement pure virtual function Initinstance. Application should define an application object in global space. MFC framework calls Initinstance using base class pointer of CWinApp from WinMain and programmer should override Initinstance. Initinstance is the callback event where programmer should define window class then register class and create top level window. Initinstance should return TRUE so that MFC framework can further process message queues and dispatch.
Programmer should create a Window object which is derived from CFrameWnd. CFrameWnd takes care of defining window class and registering it during construction. CFrameWnd provides Create() function to do window creation. Create() is a overloaded funstion and programmers need not to provide all arguments. It takes /mfc defaults if arguments are not given.
MFC Basic Steps
- Derive CWinApp and Implement Initinstance
- Define a global object of application class
- Derive CFrameWnd and declare a window class
- Allocate window object and assign to m_pMainWnd
- Call Create() or call Create() from window constructor
- Call ShowWindow() and UpdateWindow() and return true from Initinstance.
- CWinApp implements GetMessage and Dispatch message in MFC framework.
- CFrameWnd has built-in WindowProc to handle messages.
- All messages are handled by DefWindowProc of CFrameWnd
- User can declare additional message maps and handle events of their own.
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