This exception seems to be caused because the stream is not decrypted correctly and the stream data is corrupted. For instance when the stream is with FlateDecode filter the exception is InvalidDataException with message "Unknown compression method".
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.
Setting Handle property to false should result in rethrowing the exception and interrupting current RadFixedDocument rendering. This is related to Exception Handling Mechanism mentioned in this documentation article: https://docs.telerik.com/devtools/wpf/controls/radpdfviewer/document-model/exceptionhandling
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.
For some fonts the issue is present. Some of them are: KozGoPro-Medium KozMinPro-Regular KozGoPro-Bold
Enable the customers to directly save the document inside PdfViewer to a file or a stream. Available in LIB Version 2017.3.1225.
Layers represent groups of optional content which can be hidden or shown.
The Ò symbol is not found in the encoding as is rendered as a ".notdef" glyph. Available in LIB Version 2017.3.1127.
This may result in inversed transparency issue when rendering images with ImageMask. Fix available in LIB Version 2017.3.1120.
Currently, the implementation relies on the fact that the previous cross-reference value of a stream object is always a stream object. Instead during the cross-reference recursion, we should check on each step whether the previous cross-reference item is table or stream. Fix available in LIB Version 2017.3.1120.
Before starting to decode big image, try to estimate the needed memory and check if such memory is available using the MemoryFailPoint class. The behavior in case of failure in printing scenarios should be considered carefully. The user should be able to turn the behavior on and off.
Currently, the Find() method searches from the beginning of the document to its end. Enable the customer to specify a particular range of pages the method should search through.
When a page is rotated its annotations are not positioned correctly.
FixedDocumentSinglePagePresenter uses simple rendering mechanism using UIElements, which currently has some limitations: - Layers are not supported, thus annotations and forms are not rendered (even read-only) - UIElements could be affected (clipped) when UseLayoutRounding property set at parent level, when DPI is different that 96 DPI. Workaround: If content is clipped, ensure that UseLayoutRounding is set to false as presenter level: <telerikUI:FixedDocumentSinglePagePresenter UseLayoutRounding="False" />
In Adobe and Foxit readers, the user can draw different shapes, which are later saved as images in the document.
The images are loaded asynchronously and when scrolling too fast, the loader might fail to load an image if it is bigger.
When users do "copy" operation, add the content to the clipboard in RTF format. This would allow to paste the text along with its formatting in text editors like MS Word.
The appearance of such invisible annotation is not imported property and the viewer is trying to recalculate it in an infinite recursion which causes the StackOverflowException. Fix available in LIB Version 2017.3.1009.