Loading a document that contains big images could lead to OutOfMemory exception.
Import documents that use this type of encryption. Currently, a handled NotSupportedEncryptionException is thrown while importing such a document and it cannot be opened in RadPdfViewer. Available in R1 2018 Official Release version.
The feature was implemented for Q2 2014.
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.
Add support for importing and filling interactive forms. Interactive Forms content is visualized read-only in RadPdfViewer UI with R1 2017 Release Available in R3 2017 Official Release Version.
Create appropriate methods, properties and events that will allow to users to scroll the RadPdfViewer and handle the scrolling events. Introduce API that will allow to manipulate the scroll bars.
When this feature is implemented it should visualize the bookmarks similarly to in the attached screenshot. Available in R3 2018 Official Release Version.
Currently, all images are decoded and preserved in RGBA format (32 bits for each pixel). However, there are files that optimize their images by preserving them with 1 bit for each pixel. In WPF we may create monochrome System.Windows.Media.ImageSource that would optimize the performance and memory consumption when rendering such images. Available in R1 2018 Official Release Version.
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.
There is opportunity to further optimize the caching mechanism of the image sources, which will reduce the memory consumption. The fast scrolling in a document containing big images could lead to an OutOfMemoryException. Available in R1 2017 Official Release Version.