|
IPersistFile
The IPersistFile interface provides methods for an object to load and save itself in a disk
file, instead of saving itself to a storage object. Because the information
needed to open a file varies greatly from one application to another, the object
must be responsible for opening its disk file.
When to Implement
The IPersistFile interface is implemented by any object or container application that can be
linked through a file moniker, including the following:
- Any object that supports links to its files or to pseudo-objects within its files
- A container application that supports links to component objects within its
compound file
Typically, you implement the IPersistFile interface as part of an aggregate object that includes other interfaces that
are appropriate for the type of moniker binding that is supported.
For example, in either of the cases mentioned above, the moniker for the
linked object can be a composite moniker. In the first case, a composite moniker
identifies the pseudo-object contained within the file. In the second case, a
composite moniker identifies the embedded object contained within the compound
file. In either case of composite monikers, you must implement the IPersistFile interface as part of same object that also implements the IOleItemContainer interface. Then, when the application for the linked object is run, OLE
queries for the IOleItemContainer interface to locate the embedded object or the pseudo-object contained in the
file.
As another example, if the moniker is a simple file moniker (i.e., the link is
to the entire file), OLE queries for the interface that the initiator of the
bind operation requested. Typically, this is one of the compound document
interfaces, such as IOleObject, IDataObject, or IPersistStorage.
When to Use
You call methods in the IPersistFile interface to load or save a linked component object in a specified file.
When the application for the linked object is run, OLE calls the IPersistFile::Load method. Once the file is loaded, OLE calls IPersistFile::QueryInterface to get another interface pointer to the loaded object. The IPersistFile interface is typically part of an aggregate object that offers other
interfaces.
Note that OLE calls only the IPersistFile::Load method. It does not call any of the other IPersistFile methods. Typically, applications do not call these methods either. The IPersistFile::Load method enables OLE to load a file on behalf of a container application when
the container needs to run the application for the linked object. The other IPersistFile methods support saving a component to a file, but container applications do
not tell a linked object to save itself. It is entirely up to the end user and
the application for the linked object to decide when the component should be
saved. This differs from the situation for an embedded component, in which the
container application uses the IPersistStorage interface to provide the storage and to tell the component when to save
itself.
Methods in Vtable Order
IPersistFile Methods
| Description
| IsDirty
| Checks an object for changes since it was last saved to its current file.
| Load
| Opens the specified file and initializes an object from the file contents.
| Save
| Saves the object into the specified file.
| SaveCompleted
| Notifies the object that it can revert from NoScribble mode to Normal mode.
| GetCurFile
| Gets the current name of the file associated with the component.
|
| Last news from Greatis Software |
 |
|
Nostalgia .Net |
|
.Net is powerful, but not all-powerful, so sometimes we need to use Win32 API for our .Net applications. It's simple enough with Platform Invoke if you have Win32 skill, but we do not always have time to dig the ancient documentation, declare the special types that are compatible with Win32, find the values of the Win32's constants and so on. Nostalgia .Net offers several simple-to-use classes, and components that will allow you to forget about the headache of Win32 and just use the power of Win32 in your application the same way as you use the native. Net classes. More » |
| Recommended software for developers |
 |
|
Ultimate Pack |
|
Component pack for Delphi and C++ Builder that contains runtime form designer, runtime object inspector, print suite and much more for the very special price. More » |
 |
|
Form Designer .Net |
|
Unique runtime form design solution that allows to edit any form in .Net WinForms application at runtime with full source codes for only 300 euro! More » |
 |
|
Print Suite .Net |
|
Print Suite .Net is a set of components for easy printing texts, images and grids from your WinForms applications. Full C# source codes are available More » |
 |
|
Gradient Controls .Net |
|
Gradient Controls .Net offers controls with gradient background feature. Labels, panels and so on... Full C# source codes are available More » |
 |
|
Greatis iGrid |
|
iGrid plots drawing grid right over your desktop, so you can use it everywhere, with any drawing application without any special plugins for different graphic editors. More » |
All the contacts and projectsDmitry Vasiliev (just.dmitry)
Related LinksSoftware for Visual Studio .NET developers
Software for Delphi and C++ Builder developers
Software for Visual Basic 6 developers
Delphi Tips&Tricks
MegaDetailed.NET More Online Helps Win32 Programmer's Reference
Win32 Multimedia Programmer's Reference
OLE Programmer's Reference
Microsoft Windows Pen API Programmer's Reference
Microsoft Windows Sockets 2 Reference
Microsoft Windows Telephony API (TAPI) Programmer's Reference
Unix Manual Pages
|
