Loading a document that contains big images could lead to OutOfMemory exception.
The fix will be available in our official release Q1 2016.
We have a good news for all of you who have experienced problems with the memory consumption of RadPdfViewer. We have made significant optimization of what is cached for each page when scrolling in a document. Please have in mind that when using big images in a document the optimization may seem not so significant. This is because there is additional opportunity to further optimization of the caching mechanism for the image sources. I have logged this additional opportunity as a different feature request. Here is a link if you would like to subscribe for status updates of that item to: Optimize the image source cache - http://feedback.telerik.com/Project/143/Feedback/Details/189305-optimize-the-image-source-cache
Printing document on a machine with .NET Framework 4.6 installed does not work for some documents. Currently, an issue is opened at Microsoft Connect: "Printing with PrintDialog fails when .NET 4.6 is installed" (https://connect.microsoft.com/VisualStudio/feedback/details/1980419/printing-with-printdialog-fails-when-net-4-6-is-installed). Workaround: In the attached project.
Due to excessive memory consumption when decoding images, OutOfMemoryException can be thrown when viewing documents with large images inside them. Workarounds: - Set ExtensibilityManager.MaxImageSize = null. This will skip one resizing step, and could be beneficial in documents containing few large images. - Use 64-bit process for the client application. This allows the process to consume much more memory. Note that starting 64-bit process while debugging can be tricky, as described in this blog post: https://weblog.west-wind.com/posts/2016/Dec/19/Visual-Studio-Debugging-and-64-Bit-NET-Applications. Available in R1 2018 Official release version.
This exception is thrown because there is field name with special characters which are incorrectly modified during the recalculation process of widget appearances. This exception is thrown in the internal RecalculateMissingAppearances method or in RecalculateWidgetAppearancesOld method.
This happens only in scenarios when the widget has On state appearance defined and Off state appearance missing. If both appearances are missing then RadPdfViewer recalculates the appearances and the checkbox is successfully selected and deselected.
If the presenter is changed (for example, by pressing "Fit one full page to window" button) during the inertia of a scroll operation, NullRererenceException is thrown. Fix available in LIB Version 2017.2.627.
When a PDF is printed all images are omitted. Available in R1 2018 SP1 version.
Loading page with a lot of text takes several minutes which is unacceptable. This performance issue is caused by class GlypInfoFactory, which caches the glyph information. Available in LIB Version 2017.3.1225.
RadPdfViewer's AcroForm property ViewersShouldRecalculateWidgetAppearances should be respected when being set to true. In this case, RadPdfViewer should recalculate all widget appearances and this would resolve the issue with empty form field widgets after opening such PDF document.
The exception is thrown when the RadioButtonField options array contains nested arrays instead of string values. Fix available in LIB Version 2018.1.312.
The file contains the following: 68.637 604.561 455.981 -107.996 re 72.237 604.561 l S Instead of the more usual 68.637 604.561 455.981 -107.996 re S 72.237 604.561 l S Both are valid but the first seems to create a problem. Fix available in LIB Version 2018.1.319.
The Ò symbol is not found in the encoding as is rendered as a ".notdef" glyph. Available in LIB Version 2017.3.1127.