MFC Program..

[Siva Sankar Koyi]

Hi, I have my MFC wizard generated applicaiton (TestPro), one global object is created with name CTestProApp theAPP, This constructir invokes ( CWinApp::CWinApp), from here how the control flows.. From here how will call my progam ( CTestProApp->InistInstance, run..etc) methods, b'coz I did't find any of the methods are calling from CWinApp constructor. Code for CWinApp constructor: Could any body explain code level how it works, ---------------------------------------------------------------- CWinApp::CWinApp(LPCTSTR lpszAppName) { if (lpszAppName != NULL) m_pszAppName = _tcsdup(lpszAppName); else m_pszAppName = NULL; // initialize CWinThread state AFX_MODULE_STATE* pModuleState = _AFX_CMDTARGET_GETSTATE(); AFX_MODULE_THREAD_STATE* pThreadState = pModuleState->m_thread; ASSERT(AfxGetThread() == NULL); pThreadState->m_pCurrentWinThread = this; ASSERT(AfxGetThread() == this); m_hThread = ::GetCurrentThread(); m_nThreadID = ::GetCurrentThreadId(); // initialize CWinApp state ASSERT(afxCurrentWinApp == NULL); // only one CWinApp object please pModuleState->m_pCurrentWinApp = this; ASSERT(AfxGetApp() == this); // in non-running state until WinMain m_hInstance = NULL; m_pszHelpFilePath = NULL; m_pszProfileName = NULL; m_pszRegistryKey = NULL; m_pszExeName = NULL; m_pRecentFileList = NULL; m_pDocManager = NULL; m_atomApp = m_atomSystemTopic = NULL; m_lpCmdLine = NULL; m_pCmdInfo = NULL; // initialize wait cursor state m_nWaitCursorCount = 0; m_hcurWaitCursorRestore = NULL; // initialize current printer state m_hDevMode = NULL; m_hDevNames = NULL; m_nNumPreviewPages = 0; // not specified (defaults to 1) // initialize DAO state m_lpfnDaoTerm = NULL; // will be set if AfxDaoInit called // other initialization m_bHelpMode = FALSE; m_nSafetyPoolSize = 512; // default size } --------------------------------------------------------------------------- Thanks Siva

[Maximilien]

Siva Sankar Koyi wrote:

From here how will call my progam ( CTestProApp->InistInstance, run..etc) methods, b'coz I did't find any of the methods are calling from CWinApp constructor.

it's all done by the frame work. one way to look at it, is to put a break point in InitInstance, and see where it's called from. if InitInstance is not called, I think there is a problem with you program, maybe you deleted a line or two in the generated Wizard code.

---

Maximilien Lincourt Your Head A Splode - Strong Bad

[Eytukan]

press f9 on the codes you have typed and while running in the debugging mode, just press f5 so that it will stop in the next line of "your" code where you have set a break-point(f9). now it wont be letting you see the MFC AFX zone secrets.

---

VuNic