Some colors are changed due to incorrect import of some graphic state colors.

The fix will be available in our latest LIB release (v. 2015.1.0323).

When using CTRL+Mousewheel to zoom in to a PDFViewer document, it should zoom into the point where the mouse pointer is located. Currently it just does a simple zoom of the whole document.

For example see Acrobat Reader or Google Maps.

Some of the lines that should be dashed are rendered as continuous lines.

Currently, ICC version 2 and version 4 are not supported and these colors are rendered using alternative colorspace calculations.

Provide public API for accessing document properties such us Title, Author, Subject, Keywords, Creation date, etc...

The fix will be available in Q3 SP.

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 this feature is implemented it should visualize the bookmarks similarly to in the attached screenshot.

Available in R3 2018 Official Release Version.

Loading a document that contains big images could lead to OutOfMemory exception.

When an image is actually consisting of sequence of smaller images, sometimes white lines appear between the smaller images.

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 the pdfviewer is used inside backstagemenu then the pdf file content is not displayed.

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

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.