The text appears disordered due to wrong calculations of the glyph geometries.
Parsing the wrong content stream in RadPdfViewer results in handled exception and this way some of the PDF content is missing when rendering the page.
If you search in a very large file and there are no matches of the string you're searching for or the matches are very far from the start (e.g. on the 10 000th page), the search takes a lot of time. The scenario can also lead to a crash. Consider adding a progress bar showing on which page we're currently searching and implementing possibility to cancel the search.
With the current implementation, it takes seconds to decode and display JPEG with several megapixels (for example size 4000 x 2000 pixels). The memory consumption when decoding such images also needs improvements. Workaround: Custom DctDecode filter may be implemented and registered in RadPdfViewer. The attached demo shows how this may be achieved by using BitmapImage class to decode the JPEG images instead of the default RadPdfViewer's JpegDecoder.
When clicking on link annotations pointing to destinations in the document, and the "Fit one full page to window" mode is activated, the document is not scrolled exactly to the destination. The issue can be reproduced only in Single Page Presenter mode and when the Top and Left values of the passed parameter are greater than 0. The problem can also be observed by invoking directly GoToDestination method, as the problem is inside it.
The ColorSpace element is not required for images which are using JPXDecode filter.
The default WPF PrintDialog cannot print asynchronously when it is shown in UI. However, you may see the demo in this forum post showing how to create custom PrintDialog and perform async printing with it: http://www.telerik.com/forums/pdfviewer-print-makes-ui-unresponsive#js0YdzFWc0Oa8C3g6a18lg
This item is "Declined" because it is merged with another feedback item. Instead, you may follow this item: https://feedback.telerik.com/Project/143/Feedback/Details/155077-pdfviewer-text-is-displayed-as-rectangles-for-some-truetype-fonts
Using this API the some may turn the busy indicator.
Vertical lines with small length and big thickness are drawn as short horizontal lines with big StrokeThickess. This results in rendering them as big squares, which can hide parts of the content.
Some colors are changed due to incorrect import of some graphic state colors.
Currently, ICC version 2 and version 4 are not supported and these colors are rendered using alternative colorspace calculations.
Overprinting is option in the GraphicState that allows combining colors when drawing one object above another object. It is briefly described on page 284 and page 565 in PdfReference 1.7. However, the result of overprinting is device dependent and there are no strict instructions how the result should look like. This feature also includes support for the different blending modes.
When an image is actually consisting of vertical sequence of smaller images, sometimes white horizontal lines appear between the smaller images.
Word and Visual Studio allow selecting a block of text when holding down the ALT-key. It would be great, if PDFViewer could support this. It would be even greater if there could be a TextSelection constructor with page coordinates to set a region of text, which should be selected or copied.
Hi! Please extend CreateThumbnail. It is currently defined as: public ImageSource CreateThumbnail(RadFixedPage page, Size thumbnailSize) Well, it works great for thumbnails and display on screen, but for saving bitmaps it is not perfect. If I want to change the DPI settings when saving the bitmap it is not possible, also the Pixelformat is not settable because they are hardcoded in CreateThumbnail. Please extend CreateThumbnail like this: public ImageSource CreateThumbnail(RadFixedPage page, Size thumbnailSize, PixcelFormat pixelformat, int DPIX, int DPIY) By the way, opening up the API behind radFixedPage.LoadContent and the hole drawing/rendering complex would be even better :-) I'm dreaming of, to be able, only drawing certain layers. Sometimes it helps to see the hole object tree of a page to understand what gets painted over one another. Thanks!
The visualizations of all annotations are defined by their normal appearance streams. This is already implemented in RadPdfViewer for the supported annotation types (Link and Widget annotations). It may be easily adopted for not supported annotation types as well. Available in 2017 R3 Official Release Version.
Currently, RadPdfViewer uses WPF DrawingContext class for drawing page elements to a Canvas. When PDF page has many content elements (usually geometries) drawing the page may be time-consuming and freezes the UI. Instead, we should consider implementing another approach for rendering the content asynchronously which would improve the user experience.
When there is no ToUnicode CMap, the text from the Simple Font instance should be extracted by mapping the glyph name to its corresponding charcode according to Adobe Glyph List. Additionally, the Differences array should be included in these calculations when there is custom encoding. The current implementation of RadPdfViewer makes ToString to the original char id byte value which leads to wrong characters.