The class implementation also includes the definition of the Serialize() function: This is required for the proper dynamic creation of a CSketcherDoc object, including members inherited from the base class. Message maps and the rest of the file.Īll this macro does is define the base class for CSketcherDoc as CDocument. IMPLEMENT_DYNCREATE(CSketcherDoc, CDocument) #ifdef _DEBUG #define new DEBUG_NEW #endif #include “stdafx.h” #include “Sketcher.h” #include “PenDialog.h” SketcherDoc.cpp : implementation of the CSketcherDoc class The first is the macro IMPLEMENT_DYNCREATE() that complements the DECLARE_DYNCREATE() macro: There are two bits of the file containing the implementation of CSketcherDoc that relate to serialization.

Serialization in the Document Class Implementation This is also essential for serialization to work because the default constructor is used by the framework to synthesize an object when reading from a file, and the synthesized object is then filled out with the data from the file to set the values of the data members of the object. Note that the class explicitly defines a default constructor. You’ll explore this in more detail when considering the implementation of serialization for the document class. The object of type CArchive that’s passed as an argument to this function determines whether the operation that is to occur is input or output. It’s called to perform both input and output serialization operations on the data members of the class.

Every class that’s serializable must include this function. The class definition also includes a declaration for a virtual function Serialize().

The Hierarchy Chart in the Microsoft Foundation Class Reference for Visual C++ 2005 shows those classes which aren’t derived from CObject. Almost all MFC classes are derived from CObject and, as such, are serializable. This is why the CElement class was derived from CObject. For any class that you want to serialize, CObject must be a direct or indirect base because it adds the functionality that enables serialization to work. These macros apply only to classes derived from CObject, but as you will see shortly, they aren’t the only pair of macros that can be used in this context.

It’s matched by a complementary macro, IMPLEMENT_DYNCREATE(), in the class implementation. DECLARE_DYNCREATE() is a macro that enables objects of the CSketcherDoc class to be created dynamically by the application framework during the serialization input process.

Declare Serial Mfc