Creating a PdfViewer instance without adding it in the visual tree, leads to leaked document presenter instances when the TouchManager is enabled.
Workaround: Disable the TouchManager:
Telerik.Windows.Input.Touch.TouchManager.IsEnabled = false;
BT 48 819.32 Td -16.6 Ts (Some text to display) Tj ET
Currently, when we parse inline image dictionaries we rely on the assumption that the colorspace will be PdfName. However, there are files with complex colorspaces that are PdfArray and InvalidCastException is thrown. All the content after this exception is lost and not visualized by RadPdfViewer.
Add support for Lab color space. Currently alternate color is used to render the pixels, which may result in incorrect colors.
Hi Telerik Support
We use your Telerik PDF-Viewer since your last Version "UI for WPF R1 2021" which supports Type 3 fonts.
Now the version runs productive by our customers. But after a day, they found some special PDFs that doesn't work quite right with your PDF-Viewer.
In the appendix you will find the PDf-Files as samples for the bugs that i'm describing.
Because of data privacy, the PDF-Files are cutted and cropped.
Also a demo project is appended (It could also be reproduced with the demo Progress Telerik WPF UI for th PDF-Viewer).
First Problem: Blank Page
Hint: It seems that only a few PDF-Files from a specific program seems to be a problem.
Second Problem: Displaying data delayed
I would be glad for a quick possible solution for our customer.
Best regards
Serge Schoop
When importing a document containing Outlines (Bookmarks) containing Actions with an empty dictionary:
<</Title(Bookmarks)/Parent .../First .../Last .../Prev .../A<<>>/Count ...>leads to an exception thrown: System.MissingMethodException: 'Cannot create an abstract class.'
Even small documents (~30 kb) containing images encoded with CCITTFaxDecode filter can take about 10 seconds to be opened. In 2014 Q1 SP1 such documents load faster.
Implement import of documents containing Type 3 fonts.