Custom Window Class for View Window

Often I have been coding away and realized that to get exactly the behavior I would like I would need to change the Window class for my View window. Upon looking into the Developer Studio help file, and perusing the help to AfxRegisterClass, I'd realize that this could be a bit more work than one would originally think. The most recent time I went to do this I came across Zafir Anjum's example "Titletip for individual cells" in the ListView section of this code repository. Looking at what he had done for his custom window classes I realized that if I could get the class info for the default window class of the MFC View class, it would be trivial to change the settings of said class and reregister it under a new name. This is what I came up with.
#define CUSTOM_CLASSNAME _T("YourCustomClassName")

BOOL CMyView::PreCreateWindow(CREATESTRUCT& cs)
{

   // modify window styles and such here
   cs.style |= (WS_CLIPCHILDREN | WS_CLIPSIBLINGS);          
 
   // call base class PreCreateWindow to get the cs.lpszClass filled in with the MFC default class name
   if( !CView::PreCreateWindow(cs) )
     return 0;

   // Register the window class if it has not already been registered.
   
   WNDCLASS wndcls;
   HINSTANCE hInst = AfxGetInstanceHandle();

   if(!(::GetClassInfo(hInst, CUSTOM_CLASSNAME, &wndcls)))      // check if our class is registered
   {
     if(::GetClassInfo(hInst, cs.lpszClass, &wndcls))           // get default MFC class settings 
     {
	wndcls.lpszClassName = CUSTOM_CLASSNAME;                // set our class name

	wndcls.style |= CS_OWNDC;			        // change settings for your custom class
        wndcls.hbrBackground = NULL;

        if (!AfxRegisterClass(&wndcls))                         // register class
          AfxThrowResourceException();				// could not register class
     }
     else
       AfxThrowResourceException();				// default MFC class not registered
    }

    cs.lpszClass = CUSTOMVIEWCLASSNAME;                         // set our class name in CREATESTRUCT

    return 1;                                                   // we're all set
}

Date Posted: 6/24/98
Posted by: Pat Laplante.



Comments

  • Fantastic!

    Posted by Legacy on 07/30/2003 12:00am

    Originally posted by: Beau Jackson

    This is exactly what I was looking for - MFC dynamically generated window class names were giving me fits because I had to make a call to FindWindow() and you have to provide the class name.

    Thanks!

    Reply
Leave a Comment
  • Your email address will not be published. All fields are required.

Top White Papers and Webcasts

  • New IT trends to support worker mobility -- such as VDI and BYOD -- are quickly gaining interest and adoption. But just as with any new trend, there are concerns and pitfalls to avoid. Download this paper to learn the most important considerations to keep in mind for your VDI project.

  • What if you could rapidly grow your business while eliminating the complexity and multiple operating systems, administration and management tools, and security and compliance requirements? See how many good things happen when you standardize on open, flexible infrastructure solutions.

Most Popular Programming Stories

More for Developers

RSS Feeds

Thanks for your registration, follow us on our social networks to keep up-to-date