checked it class by class. That's what's driving me nuts..
"Joseph M. Newcomer" <newcomer@flounder.com> wrote in message
Generally, hand-editing changes like this is dangerous. My own approach
would be to
create a whole new project based on the "Ex" style, then use something
like windiff or
some similar source-compare tool to compare key modules of the new
project with the old
project, and make sure that all the appropriate code (that is, any code
I did not write)
is the same in both projects. Generally, just simple hand-edits are not
really sufficient
to guarantee that everything will work as expected. Otherwise, I'd not
offer an opinion
on what might have gone wrong because until I did the source-compare of
the critical
modules I wouldn't know if my hand-edits had captured all the
essentials.
joe
On Mon, 13 Jul 2009 20:20:03 -0500, "Rick Ruhl" <ricker@cssincorp.com>
wrote:
Im getting a ASSERT on File/New
Code was changed as follows:
CWinApp to CWinAppEx
CMDIChildWnd to CMDIChildWndEx
CMDIFrameWnd toCMDIFrameWndEx
etc etc
I do the following
m_pDocTemplate = new CMultiDocTemplate(
IDR_DXTERMTYPE,
RUNTIME_CLASS(CDXTermDoc),
RUNTIME_CLASS (CSession), // csession is the CMDIChildWndEx
RUNTIME_CLASS(CTextView));
m_pDocTemplate->SetContainerInfo(IDR_MAINFRAME);
AddDocTemplate(m_pDocTemplate);
CSession does have a splitter windows in it. CMysplitter derived from
CSplitterWndEx
So when I do a file/new I can get to the constructor of
CSession::CSession
and trace through that, but then I get an assert
in winmdi.cpp at line 504, which is
ASSERT(::IsWindow(pParentWnd->m_hWndMDIClient));
All this worked before I moved to the new classes, have I missed
anything?
Thanks
Rick
Joseph M. Newcomer [MVP]
email: newcomer@flounder.com
Web: http://www.flounder.com
MVP Tips: http://www.flounder.com/mvp_tips.htm