Toolkit Release Notes 2016 R1.3


This Toolkit 2016 R1.3 release (Build 2016.1.3.17145) includes bug fixes and an enhancement.
The bug fixes from the two interim releases are also included.



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 Windows® XP

  • 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.


Enhancements


The GetInputFields property now has a parameter that allows you to choose how to sort the collection of field instances that are returned. You can choose to sort by the alphabetical order of the field name, the tab order, or by the x/y location on the page.


Latest Bug Fixes


The following bugs were resolved since the last interim Toolkit release.
























































ID #



Description



Resolution



2566



When BarWidthReduction was used to reduce the width of a barcode in the input file, the width of the barcode in the output PDF did not change.



Changes were made to the code implementing barcode-width reduction. This resolved this issue.



2627
2879
3664



When digitally signing a PDF containing compressed object streams, the output file was corrupted.



Changes made to the code related to object compression and signature fields resolved these issues.



14584



When PrintMultilineText was called after StitchPDF using the source file containing Arial font, the output PDF displayed garbled text.



Changes made to the code related to font caching resolved this issue.



14589



File specific: When SetInputPasswords was used with CopyForm, the file could not be opened.



Changes made to the code related to how encryption is handled resolved this issue.



14627



After calling PrintMultilineText, the last line of text was missing in the output PDF.



Changes made to the code related to how the y position for the next line was calculated resolved this issue.



14666



File specific: After calling OpenInputFile to open a file using a blank password, the file would not open.



Changes made to the code related to how the internal File ID was handled resolved this issue.



14670



When looping through fields using GetInputFields, the field instances were not returned.



Changes made to the code related to how string values were initialized resolved this issue.



14709



If XMP.SetCustomProperty included a space in the data for the sKey parameter, when the output PDF was opened with a Reader, the display of the custom property was truncated at the position of the space.



Changes made to the code related to how dictionary and XMP names are handled resolved this issue.



14796



When files containing barcodes were converted, the output PDF file size was larger than it was when converted using Toolkit 2011.



Changes made to the code related to image compression resolved this issue.



Bugs Fixed in Interim Release Build 2016.1.2.17103


The following bugs were resolved since the prior interim Toolkit release.





















ID #



Description



Resolution



13246



After using the PDFVersion property to select versions less than 1.5, the output PDF displayed PDF Version 1.5 in the Document Properties dialog box.



Changes to the code related to how Toolkit handles object compressions resolved this issue.



14688



File specific: When CopyForm was used to convert this file, the reader displayed an error message, "The font 'Arial' contains a bad /BBox" when the output PDF was opened.



Updates to the code resolved this issue.



Bugs Fixed in Interim Release Build 2016.1.2.17083


The following bugs were resolved since the initial Toolkit 2016 release.







































































ID #



Description



Resolution



2645



File specific: When ImageToPDF was called to convert this corrupted .gif file, CPU usage went to 100% while Toolkit continued to attempt a conversion, and did not report an error.



This issue was resolved by updates to the code, and now Toolkit ends the task and reports an error as expected.



3016



File specific: When LinearizeFile was used after encryption, the output file was corrupt.



Code updates related to how the object stream is handled resolved this issue.



3249



When iteratively merging or form filling the same file from a sample application, Toolkit's memory appeared to progressively accumulate. This was not a memory leak; over successive runs, the memory accumulated proportionately and then stabilized.



General updates to the code resolved this issue.



4128



File specific: After a PDF with a logo was merged, the output PDF displayed corrupt characters and returned an error "Cannot extract the embedded font".



Code changes related to how font resources are handled resolved this issue.



4453



File specific: This file had buttons that were set to be invisible after conversion, but some buttons remained visible in the output PDF.



Code changes related to how Toolkit handles missing references resolved this issue.



4507



File specific: After converting a compressed TIFF image, the output PDF displayed an error message, "Insufficient data for an image" when opened with Acrobat Reader.



The IgnoreCompression parameter was added to the TIFFToPDF method, which resolves this issue.



4689



After calling ParseDataStream, in the output PDF, the data in fields was misaligned and extended outside the field.



Code changes related to how font widths are handled resolved this issue.



4746



File specific: After this PDF file was linearized by Toolkit, when the output PDF was opened, a message displayed reporting: "the page may not display correctly", even though the page displayed correctly.



General updates to the code resolved this issue.



10050



File specific: When tab characters ("\t" ) were included in the data field string for SetFormFieldData, the output PDF displayed small boxes instead of tab spaces.



The code was updated to handle tab characters.



10078



File specific: When StitchPDF was called to combine two PDFs onto one page, the output PDF contained only one of the PDFs.



General updates to the code resolved this issue.



12475



When using PrintImage to add .wmf images to a PDF, the images in the output PDF did not display as expected.



The code related to image conversions was updated to process .wmf images more efficiently.



14408



When using TIFFToPDF, the TIFF file remained locked even though Toolkit's object was destroyed in the script. This prevented the TIFF file from being deleted.



Code updates related to handling TIFF conversions resolved this issue.



Note: For a list of Known Bugs, see:


https://www.activepdf.com/support/kb-special/kb-bug-report/toolkit-known-bugs-2016-r1-3


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:


https://www.activepdf.com/support/documentlinks.