22.03.2015 Views

DLI Implementation and Reference Guide - Datalogics

DLI Implementation and Reference Guide - Datalogics

DLI Implementation and Reference Guide - Datalogics

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

A.46 <strong>DLI</strong> <strong>Reference</strong> <strong>Guide</strong><br />

dlpdfdocdestroy (DLPDFDOC *Doc)<br />

Return Value: void<br />

Concepts <strong>and</strong> Facilities: <strong>Guide</strong> to the DL Pager Composition System<br />

Description<br />

Parameters<br />

Return Value<br />

Destroys the specified document, releasing all<br />

resources used in the document.<br />

DLPDFDOC *Doc: represents the document<br />

structure <strong>and</strong> the current status of the document<br />

at all times.<br />

void<br />

Exceptions<br />

Header<br />

Related Methods<br />

Availability<br />

dli.h<br />

dlpdfdoccreate,<br />

dlpdfinstancesetgrcachelimits<br />

All <strong>DLI</strong>-supported platforms.<br />

Technical Notes<br />

1 All documents should be destroyed before terminating <strong>DLI</strong>.<br />

2 A pointer to a DLPDFDOC structure is invalid <strong>and</strong> should not be used after calling<br />

dlpdfdocdestroy for that structure.<br />

3 The collection of information regarding where elements lie within a document is<br />

the responsibility of the composition engine. <strong>DLI</strong> cannot provide assistance with<br />

this.<br />

4 If dlpdfinstancesetgrcachelimits had been set previously, the graphics<br />

cache size is evaluated at this time, <strong>and</strong> graphics are purged if the cache size<br />

exceeds its preset high-water mark limit.<br />

5 If applicable, dlpdfdocdestroy removes the Files In Memory file representing<br />

the <strong>DLI</strong> document if no h<strong>and</strong>le has been acquired to the file in memory.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!