Frameworks
Integrations
Mendix
SharePoint
Default UI
Modular UI
AnnotationManager
Annotation Types
Customize
Version 11
Version 10
v10.12
v10.11
v10.10
v10.9
v10.8
v10.7
v10.6
v10.5
v10.4
v10.3
v10.2
v10.1
v10.0
Version 8
v8.12
v8.11
v8.10
v8.9
v8.8
v8.7
v8.6
v8.5
v8.4
v8.3
v8.2
v8.1
v8.0
Version 7
Version 6
v6.3
v6.2
v6.1
v6.0
Version 5
Version 4
Version 3
Version 2
WebViewer Server
WebViewer BIM
A PDF can be loaded into a Document or PDFDoc object using their respective functions to acquire the document data.
To get document data by creating a new Document
object, the following example shows how to use a createDocument
to retrieve document data from an external URL.
Document
objects also have a getPDFDoc
function for retrieving an associated PDFDoc
object. However getFileData
is preferred over saveMemoryBuffer
in most cases because getFileData
gives easy control over the output and is safer (it ensure everything is loaded and it take care of locks). The only reason to use saveMemoryBuffer
over getFileData
, is if there isn't an easy way of acquiring a Document
object or if you need other PDFDoc
features for controlling the download process.
Another way of getting document data is by using the saveMemoryBuffer
function found on PDFDoc
objects. An example can be found below
After acquiring a PDFDoc
object, use the saveMemoryBuffer
function to retrieve the document data. saveMemoryBuffer
takes in an enum flag similar to getFileData
flags. The flags can be found in PDFNet.SDFDoc.SaveOptions
and their values are:
e_remove_unused
e_hex_strings
e_omit_xref
e_linearized
e_compatibility
There is also an e_incremental
flag but it's ignored when using saveMemoryBuffer
. saveMemoryBuffer
modifies the PDFDoc
data stored in memory, so it's best practice to acquire a write lock for the document.
Did you find this helpful?
Trial setup questions?
Ask experts on DiscordNeed other help?
Contact SupportPricing or product questions?
Contact Sales