Re: Document Template question

From:

Goran <goran.pusic@gmail.com>

Newsgroups:

microsoft.public.vc.mfc

Date:

Fri, 19 Jun 2009 02:01:01 -0700 (PDT)

Message-ID:

<bda3df43-ac2b-400f-a63e-5de6fb333fe4@n30g2000vba.googlegroups.com>

AddDoctemplate(NULL), in InitInstance; done.

This went completely over my head - why would the NULL arg work?

In MFC sources, void CDocManager::AddDocTemplate(CDocTemplate*
pTemplate)

        // // ******Works beacuse MFC people wrote it so that it works
    if (pTemplate == NULL)
    {
        if (pStaticList != NULL)
        {
            POSITION pos = pStaticList->GetHeadPosition();
            while (pos != NULL)
            {
                pTemplate = (CDocTemplate*)pStaticList->GetNext(pos);
                AddDocTemplate(pTemplate);
            }
            delete pStaticList;
            pStaticList = NULL;
        }
        bStaticInit = FALSE;
    }

There's pStaticList, bStaticInit and related crap in CDocTemplate and
CDocTemplateManager that make this work.

Heck, I would guess any system font used by a process is a one-off.

Again, ?

For whatever fonts are used as "defaults", my guess is there's only
one per process or something like that, and it's shared. E.g. dialog
controls there's potentially many of these in the process - it's plain
silly that each control has it's own font, when huge majority of these
are same.

Goran.