Toolkit Release Notes 2016 R2.0
This Toolkit 2016 R2.0 release (Build 2016.2.0.17264) includes updates to the code for the InitialViewInfo class, in addition to the bug fixes and new features included in Build 2016.2.0.17246.
Note: This is the second release for Toolkit 2016 R2.0, and replaces Build 2016.2.0.17246.
- Software Requirements
- Hardware Requirements
- New Features
- Bug Fixes
- Installation and Getting Started
- API Reference
Software Requirements
The following software is required to successfully use Toolkit.
Server
- Windows Server® 2008 (32- or 64-bit edition) OR
- Windows Server® 2008 R2 OR
- Windows Server® 2012 R2
- Microsoft® .NET Framework is required to use Toolkit's .NET component
(1.1 or 2.0 minimum — if .NET is not detected during installation, you are offered the option to have .NET installed for you.)
Desktop
(32- or 64-bit editions)
- Microsoft Windows® 7, 8, 8.1; OR
- Microsoft Windows VistaTM OR
- Microsoft® .NET Framework is required to use Toolkit's .NET component
(1.1 or 2.0 minimum — if .NET is not detected during installation, you are offered the option to have .NET installed for you.)
Hardware Requirements
The minimum hardware requirements for Toolkit are:
Server and desktop
- 125 MB of RAM
- 25 MB of hard disk space (for application)
Note: 2 GB is the maximum file size for PDFs handled by Toolkit in 32-bit applications.
New Features In Toolkit 2016 R2
- Control the encryption of XMP Metadata
You can use the new EncryptMetadata property to keep XMP metadata unencrypted when using encryption calls such as EncryptPDF or SetPDFSecurity. This allows you to search and index the metadata of an encrypted PDF without requiring a password. (The default state is to encrypt the metadata.)
- Set the initial view for a PDF
The new IntialVIewInfo class allows you to customize the display of a PDF when it is first opened. Use the IntialVIewInfo properties to control such options as page layout, PDF window size, and setting an opening page number. To see information about each property, In the left navigation bar, go to:
Technical Reference > InitialViewInfo Object > InitialViewInfo Properties
- Add RGB Color to lines
You can use the new SetLineColor method to specify a color when creating a line with the MoveTo and DrawTo methods.
- Check which duplex mode is used by a PDF
The new GetDuplexMode method retrieves the duplex mode used by the input PDF.
- Remove hyperlinks from a PDF
Use the new RemoveHyperlinks property to remove links to outside and/or inside targets.
- Specify which input field instance, previously stored in XMP, to collect information from
When input fields have the same name, use the GetXMPFieldInfoto method's new nInstance parameter to specify which input field to target.
For more details, see the Toolkit API manual.
Bugs fixed since Toolkit 2016 Interim Release 1.4
The following bugs were resolved since the last Toolkit release.
ID # | Description | Resolution |
4620 | After using AddLogo, the output file displays an error message when opened with Acrobat Version 8 or earlier. | General updates to the code resolved this issue. |
13039 | After calling MergeFile, the output PDF uses different font in the signature field. | Updates to the code related to font handling in signature fields resolved this issue. |
14326 | After calling MergeFile to merge three PDFs, the custom properties metadata included in one PDF was missing in the merged output PDF. | Toolkit now checks for custom field data before merging files, which resolves this issue. |
14830 | If the NumPages method is used, the output PDF increases output file size. | Updates to the code related to how font objects are generated resolved this issue. |
14921 | When the DisableFontCache property is called, it has no effect, and font is cached. | Updates to the code related to font handling resolved this issue. |
14994 | The Toolkit installer did not install the redistributable package correctly. | Updates to the installer resolved this issue. |
15168 | When creating output PDF files, Toolkit sometimes duplicated font embedding, resulting in larger than expected file sizes. | Updates to the code related to font caching resolved this issue. |
15323 | When PrintMultilineText is used with a file containing Arial font, the output PDF displays boxes instead of text. | General updates to the code resolved this issue. |
12403 14770 15252 | These file specific bugs were also fixed. | These issues are now resolved. Please contact customer support for further information. |
Bugs Fixed in Toolkit 2016 Interim Release 1.4
ID # | Description | Resolution |
15103 | When GetTextWidth was called with a blank page parameter after calling SetFont and PrintText (also with blank page parameters), the return value was twice the correct size.
| General updates to the code resolved this issue. |
15269 | When the source file contains duplicate field names, any custom JavaScript is deleted when after calling CopyForm or MergeFile. | Updates to the code concerning duplicate field names resolved this issue. |
15191 | When ParseDataStream was called, fields with duplicate names were not populated. | General updates to the code resolved this issue. |
4721 15110 15248 | These file specific bugs were also fixed. | These issues are now resolved. Please contact customer support for further information. |
Note: For a list of Known Bugs, see Toolkit Known Bugs 2016 R2.0.
Documentation
The ActivePDF Help documents are not shipped with the product. The manual listed below is posted online so that the most current and accurate information is always available.
Installation and API Reference
Installation and API information is available in the Legacy documentation section for Toolkit API Reference Guide at: