| 1-949-236-6510 | |
|
|
|
|
|
|
||||
With the release of 11.0.0.7 (April 2018) we have added Multiple Selection to the WebDocumentThumbnailer control
Please see the following KB article for full details:
INFO: WebDocumentThumbnailer Multi Select (New in 11.0.0.7)
As of Fixpack 10 (v11.0.0.10.507), we've updated our Tesseract3Engine OCRResources. We used Tesseract 3.02 previously, but a fix for a SystemAccessViolationException required that we move to 3.04
Please see: INFO: Tesseract Resources (Tessdata) d to 3.04 in 11.0.0.10
| Old File | New File |
| jquery-1.7.1.min.js | jquery-1.11.0.min.js |
| jquery-ui-1.8.14.custom.css | jquery-ui-1.10.4.min.css |
| jquery-ui-1.8.14.custom.min.js | jquery-ui-1.10.4.min.js |
| clipboard.js | -- removed -- |
| clipboard.min.js | clipboard.min.js (re-added in 11.0.0.2.00358) |
This means you will need to update your script references from
to
The Jp2Encoder (For encoding Jpeg2000 files and for using Jpeg2000 compression) was discovered to throw an exception when attempting to use less common WavletFilterMethod settings. When engineering analyzed the situation, they realized that fixing it would cause a breaking change for existing Jp2Encoder users and changing several default settings. Therefore, the decision was made to deprecate the Jp2Encoder class but keep it in DotImage... and provide a replacement Jpeg2000Encoder which had the correct properties and settings to allow for less common configuration settings
While you do not need to change your solution to use Jpeg2000Encoder unless you're receiving exceptions on save due to WavletFilterMethod and other advanced settings, it is recommended to use the Jpeg2000Encoder if possible
Also note, the Legacy Demos will be getting updated to use the Jpeg2000Encoder which means that if you are using 11.0.0.2 or earlier you will not be able to compile as the Jpeg2000Encoder class is not present until 11.0.0.3 -you can resolve this issue by changing any instance of Jpeg2000Encoder in the code back to use Jp2Encoder instead
Users that use Web Resources folders with older ASP.NET controls (This does NOT apply to WebDocumentViewer or WebCapture) may note that the following files are missing
C:\Program Files (x86)\Atalasoft\DotImage 11.0\bin\WebResources\ajax-loader_drk.gif
C:\Program Files (x86)\Atalasoft\DotImage 11.0\bin\WebResources\AtalaCanvas.js
C:\Program Files (x86)\Atalasoft\DotImage 11.0\bin\WebResources\Background_Splash.gif
C:\Program Files (x86)\Atalasoft\DotImage 11.0\bin\WebResources\ClientTools.js
C:\Program Files (x86)\Atalasoft\DotImage 11.0\bin\WebResources\CommentMinimized.png
C:\Program Files (x86)\Atalasoft\DotImage 11.0\bin\WebResources\Enums.js
C:\Program Files (x86)\Atalasoft\DotImage 11.0\bin\WebResources\excanvas-compressed.js
C:\Program Files (x86)\Atalasoft\DotImage 11.0\bin\WebResources\mask.png
C:\Program Files (x86)\Atalasoft\DotImage 11.0\bin\WebResources\spacer.gif
C:\Program Files (x86)\Atalasoft\DotImage 11.0\bin\WebResources\WebAnnotation.js
C:\Program Files (x86)\Atalasoft\DotImage 11.0\bin\WebResources\WebAnnotationController.js
C:\Program Files (x86)\Atalasoft\DotImage 11.0\bin\WebResources\WebAnnotationViewer.js
C:\Program Files (x86)\Atalasoft\DotImage 11.0\bin\WebResources\WebAnnotationViewerSplash.gif
C:\Program Files (x86)\Atalasoft\DotImage 11.0\bin\WebResources\WebImageViewer.js
C:\Program Files (x86)\Atalasoft\DotImage 11.0\bin\WebResources\WebImageViewerChild.js
C:\Program Files (x86)\Atalasoft\DotImage 11.0\bin\WebResources\WebImageViewerSplash.gif
C:\Program Files (x86)\Atalasoft\DotImage 11.0\bin\WebResources\WebThumbnailViewer.js
C:\Program Files (x86)\Atalasoft\DotImage 11.0\bin\WebResources\WebThumbnailViewerChild.js
C:\Program Files (x86)\Atalasoft\DotImage 11.0\bin\WebResources\WebThumbnailViewerSplash.gif
C:\Program Files (x86)\Atalasoft\DotImage 11.0\bin\WebResources\Zoom.cur
C:\Program Files (x86)\Atalasoft\DotImage 11.0\bin\WebResources\ZoomIn.cur
C:\Program Files (x86)\Atalasoft\DotImage 11.0\bin\WebResources\ZoomOut.curThis is a known issue and should be addressed in 11.0.0.2 in end of October 2017
In the meantime, we've attached WebResources_11.0.0.1.00338.zip to this case
Atalasoft changed to a new PDF engine in 11.0. Due to internal reasons, we need to extract the Atalasoft.PDFium.dll into the TEMP directory of the current user's profile.
For the vast majority of users, this should be completely transparent. However, if you have a particularly locked down system and receive permissions errors relating to the Atalasoft.PDFium.dll or the temp folders, here is the information you will need to resolve the issue:
For windows users/apps running under "normal" accounts that would be c:\users\YOUR_NAME\AppData\Local\Temp\
(full path would be c:\users\YOUR_NAME\AppData\Local\Temp\Atalasoft\DotImage\VERSION_NUMBER\x86orx64\Atalasoft.PDFium.dll )
For services running under system accounts.. including web applications under IIS, the user account that runs it may be a non-interactive account without a profile. In those cases it falls back on
c:\Windows\TEMP\
(full path would be c:\Windows\TEMP\Atalasoft\DotImage\VERSION_NUMBER\x86orx64\Atalasoft.PDFium.dll )
If you're encountering this in a web app or service, your other option would be to ensure that the user running the IIS process / windows service has an actual user profile of its own and that each app has a unique user.
For applications with appl.config, the entry is done there along these lines:
For web apps and services that have a web.config, you need to add the correct sections:
Or, if you're using IIS 7.5, it is possible to configure temp folder for each app
https://serverfault.com/questions/350550/is-it-possible-to-configure-the-location-of-temporary-asp-net-files-folder-in
DotImage 11.0 includes an entirely new PdfReader assembly.
Users with existing PRS2 / PRSX2 licenses will be issued new PRP2 / PRPX2 serial numbers automatically.
PRP2 / PRPX2
PRP2 / PRPX2 serials instead of their PRS2 / PRSX2 serials.
If you are a currently licensed user of the PdfReader add-on and have existing PRS2 / PRSX2 serials under maintenance, and have not received your new PRP2/PRPX2 serial(s) from Atalasoft, please check with the person within your company who handles the Atalasoft billing/renewals.
If you're unsure of who within your company would have received the updated serials, you may open a support ticket and we can assist.
NOTE: if you need to activate / license a 10.7 or older DotImage with PdfReader, you will need to use your PRS2 / PRSX2 serial(s) as the PRP2 / PRPX2 serials are only for 11.0 and newer.
As a "side effect" of updating to the newer Pdfium engine, we now can support PDF files > 2 GiB in size (previously even on 64 bit systems, the max size for a PDF file was 2 GiB due to the use of signed 32 bit integers for stream position pointers internal in the PdfReader library
This limit is no longer in place, so you should be able to read from/ write to PDF files up to 4 GiB in size
The DevelopersGuide.pdf which comes with DotImage (C:\Program Files (x86)\Atalasoft\DotImage 11.0\Help\DevelopersGuide.pdf) no longer contains client-side JavaScript API documentation for WebDocumentViewer and WebDocumentThumbnailer. that documentation has been moved to
WebDocumentViewer JavaScript API:
https://atalasoft.github.io/web-document-viewer/
Additionally, we are no longer shipping WingScan API Reference.pdf in the WebCapture Resources folder:
C:\Program Files (x86)\Atalasoft\DotImage 11.0\bin\WebResources\WebCapture
That documentation has been moved to:
WebCaptureService (WingScan) JavaScript API:
https://atalasoft.github.io/web-capture-service/
DotImage has shipped with .NET 2.0 dlls since version 6.0 and with .NET 4.0 dlls since version 9.0. Microsoft is dropping support for .NET frameworks 2.0 and 3.0 and also for .NET 4.0, 4.5, and 4.5.1.
We have support for ASP.NET Core targeting .NET Framework for our WebDocumentViewer and WebCapture components.
Please see [FAQ: Support for ASP.NET Core / .NET Core]https:
NOTE: we do not support .NET Core native (full .NET Core) just the ASP.NET Core subset when targeting .NET Framework with our modern web controls. There is no support for ASP.NET Core or .NET Core for our legacy web controls or any other controls.
We've added annotation burning to WebDocumentViewer. to use this feature, you need to set the burn property of a given annotation to "true" and update the annotation. Then on save, the annotation will be burned to the saved document instead of saved in annotation data.
now, when you call save on the viewer, any annotations with burn=true will be burned to the image
11.0 introduced the new feature of being able to reload a single changed page in the WebDocumentViewer and WebDocumentThumbnailer controls
If using WDT with WDV, then calling
_thumbs.document.reloadPage(pageIndex);
will reload the thumbnail
_viewer.document.reloadPage(pageIndex);
will reload the Web Document Viewer page
PdfGeneratedDocument now has a new ImportPages feature designed to easily allow for importing pages from additional external PDFs.
PdfDocument can not combine PDFs where more than one of the documents has AcroForm elements. The new ImportPages feature of PdfGeneratedDocument includes conflict resolution events to allow for handling such cases
Q10428 - HOWTO: CombineMultiple PDF Files With Fillable Forms (AcroForms)
Quick Example: