Represents a collection of LEADDocument objects.
function lt.Document.DocumentDocuments
extends LeadCollection
class lt.Document.DocumentDocuments
extends LeadCollection
DocumentDocuments manages the children of the document. It can be accessed through the Documents property of LEADDocument.
DocumentDocuments derives from LeadCollection. You can use any of the collection methods to iterate through the documents. This collection is read-only however and you cannot add, remove or change the items. Instead, use Pages to add or remove pages that belong to a separate document to this one. The LEADDocument.Documents collection will automatically gets updated to reflect what child documents are currently held in the document.
Here is an example that shows what happens to LEADDocument.Documents when pages are added and removed:
When document (virtualDocument
is created, LEADDocument.Documents is an empty collection
The user creates a new empty page using CreatePage of virtualDocument
and then adds it to the
LEADDocument.Pages collection. The LEADDocument.Documents collection will still be an empty
collection since the page original owner is the same document (in other words, DocumentPage.Document is virtualDocument
The user add a page from another document (document1
) into LEADDocument.Pages of virtualDocument
.
The LEADDocument.Documents collection will contain a single item: document1
The user add another page from document1
into LEADDocument.Pages of virtualDocument
.
The LEADDocument.Documents collection will still contain the single item document1
since both pages has the same owner
The user add a page from document2
into LEADDocument.Pages of virtualDocument
.
The LEADDocument.Documents collection will contain two items document1
and document2
The user removes this last page from virtualDocument
. The LEADDocument.Documents collection will
be containing the single item document1
The user removes all the pages from virtualDocument
. The LEADDocument.Documents collection will
be to being empty
When DocumentFactory.SaveToCache is called, the document will store the IDs of all the child documents.
When DocumentFactory.LoadFromCache is called, the document will try to re-load all the child documents and automatically set them in this collection. If any document fails to load or is no longer available in the cache, then all its pages are removed automatically and are nor loaded.
When the document is disposed, the value of AutoDisposeDocuments is examined, and if its true, then all the child documents are disposed as well.
For an example, refer to DocumentFactory.Create.
Help Collections
Raster .NET | C API | C++ Class Library | HTML5 JavaScript
Document .NET | C API | C++ Class Library | HTML5 JavaScript
Medical .NET | C API | C++ Class Library | HTML5 JavaScript
Medical Web Viewer .NET
Multimedia
Direct Show .NET | C API | Filters
Media Foundation .NET | C API | Transforms
Supported Platforms
.NET, Java, Android, and iOS/macOS Assemblies
Imaging, Medical, and Document
C API/C++ Class Libraries
Imaging, Medical, and Document
HTML5 JavaScript Libraries
Imaging, Medical, and Document