GoToPage() method is not working correctly in some cases when called in DocumentChanged event handler. The known cases are described below:

   1. When RadPdfViewer and the document are loaded initially and document is set through the RadPdfViewer.Document property.
Workaround: DocumentSource property could be set (in XAML or in code-behind) instead of the Document property. If the Document property is used, this should be done after RadPdfViewer is loaded.

    2. When the ScaleMode is changed in DocumentChanged event handler and then GoToPage() method is called in the same event handler.

When text is exported from PDF document using the TextFormatProvider (it's also used internally for the Copy operation), it is automatically split to lines using the vertical position of the words on the page, and small tolerance. 

Currently the tolerance is hard-coded to 0.1 pixels, which is not suitable for documents which contains scanned and OCR-ed text, and there the text lines could be slightly inclined. The result is that words on one slightly inclined line are recognized as if they are on separate lines.

This allows specifying a soft mask in the external graphics state.

"Save As" is common functionality in most of the popular PDF Viewers. It should save the currently loaded document to a file.

Workaround: Currently there is SDK demonstrating how to add such functionality: https://github.com/telerik/xaml-sdk/tree/master/PdfViewer/PdfViewerCustomSaveCommand

Available in R3 2017 Official Release Version.

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.

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.

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.

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.

The slow performance when creating thumbnail is only reproducible with specific documents.

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.

This mode allows users to show two pages of the document side by side. With the current API this may be achieved by implementing Custom Presenter.

The issue occurs when RadPdfViewer is measured in infinite space, for example:
- Added to StackPanel.
- Added to RadWindow with Auto dimensions.

Workaround: Width and Height of RadPdfViewer can be set.