[Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 594
  • Last Modified:

CSingleDocTemplate

An SDI application has a default CMyAppView generated by MFC. It is modified to have a splitter window. The left pane uses CLeftView and the right pane uses CRightView.

Which view should i use in the document template constructor in the InitInstance() and why?

BOOL CMyApp::InitInstance()
{
  //...
  // Establish the document type
  // supported by the application

  AddDocTemplate( new CSingleDocTemplate( IDR_MAINFRAME,
        RUNTIME_CLASS( CMyAppDoc ),
        RUNTIME_CLASS( CMyFrameWnd ),
        RUNTIME_CLASS( ????? ) ) );
       // ...
}

TIA
0
engllf
Asked:
engllf
  • 2
1 Solution
 
mulengaCommented:
You can use either CLeftView or CRightView, it doesn't matter since you
will need to override CMyFrameWnd::OnCreateClient().

In OnCreateClient() you will need to create a static splitter window
with two columns.  After creating the splitter window, you can then
create the two views.


Assuming that you used CRightView in your call to AddDocTemplate, then
you OnCreateClient will be similar to:

BOOL CMyFrameWnd::OnCreateClient(LPCREATESTRUCT lpcs, CCreateContext* pContext)
{
    CRect rect;
    GetClientRect(&rect);
    int width = rect.Width()/2;
    int height = rect.Height();
    CSize size(width, height);

    // create static splitter with 1 row and 2 columns
    if ( !m_wndSplitter.CreateStatic(this, 1, 2, WS_CHILD|WS_VISIBLE ) )
        return FALSE;

    // create the Left View
    if ( !m_wndSplitter.CreateView( 0, 0, RUNTIME_CLASS(CLeftView), size, pContext) )
        return FALSE;

    // Now create the right view
    if ( !m_wndSplitter.CreateView( 0, 1, pContext->m_pNewViewClass, size, pContext ) )
        return FALSE;

    return TRUE;
}
0
 
engllfAuthor Commented:
Hi,

what is the consequences of i do this?

BOOL CMyApp::InitInstance()
{
 //...
    AddDocTemplate( new CSingleDocTemplate( IDR_MAINFRAME,
      RUNTIME_CLASS( CMyAppDoc ),
      RUNTIME_CLASS( CMyFrameWnd ),
      RUNTIME_CLASS( CMyAppView) ) ); // neither CLeftView nor CRightView

  // ...
}

and

BOOL CMyFrameWnd::OnCreateClient(LPCREATESTRUCT lpcs, CCreateContext* pContext)
{
  ...  

   // create the Left View
   if (!m_wndSplitter.CreateView(0,0, RUNTIME_CLASS(CLeftView), size, pContext))
      return FALSE;

   // Now create the right view
   if (!m_wndSplitter.CreateView(0,1,RUNTIME_CLASS(CRightView), size,pContext))
      return FALSE;

   ...
}

TIA
 
0
 
smithcCommented:
It won't matter at all.  I have a similar application and I have
tried it with and without using the "passed in context".  The code that you have written should work. One question: Why would you pass in a view that you don't plan on using?
0
 
engllfAuthor Commented:
Good question. I will delete straight away... : )
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now