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

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.

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.

Add support for interactive forms based on the Adobe XML Forms Architecture (XFA). XFA specifies an XFA resource, which is an XML stream that contains the information of the form. The format of an XFA resource is described in the XML Data Package (XDP) Specification. The XFA resource provides most of the information about the form; in particular, all form-related events such as calculations and validations.

Allow passing specific pages (e.g. "1, 4, 6") and more than one page range (e.g. "1-3, 6-7") to the print dialog`s Pages page range.

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! 

Workaround for documents generated with PdfProcessing: When drawing lines using the FixedContentEditor the IsFilled graphic property should be set to false:

RadFixedDocument document = new RadFixedDocument();

Rect rect = new Rect(0, 0, 50, 50);
FixedContentEditor editor = new FixedContentEditor(document.Pages.AddPage());
editor.GraphicProperties.IsFilled = false;
editor.GraphicProperties.IsStroked = true;

editor.Position.Translate(50, 50);
editor.GraphicProperties.StrokeColor = new RgbColor(255, 0, 0);
editor.DrawText("Lines");
editor.DrawLine(rect.TopLeft, rect.TopRight);
editor.DrawLine(rect.TopRight, rect.BottomRight);
editor.DrawLine(rect.BottomRight, rect.BottomLeft);
editor.DrawLine(rect.BottomLeft, rect.TopLeft);

This may allow someone to notify the users.

Represents Free text PDF content.

Since LIB Version 2017.3.925 annotations of type FreeText can be visualized.

RadPdfViewer does not read image resources defined in Form XObject elements.

Introduce support for Sticky Note Annotation.

Expose a button in the UI that can be used instead of Ctrl+F.

Such a button can be currently added by customizing the default toolbar. For more information, check the documentation that describes how to achieve that: https://docs.telerik.com/devtools/wpf/controls/radpdfviewer/default-ui#customizing-the-default-ui

At this point, the Print() method allowing the customers to silently print a document uses the PrintableAreaWidth and PrintableAreaHeight properties of the print dialog, which are read-only and cannot be changed through the API. Consider changing them with PrintTicket.PageMediaSize.

We should also consider the scenario when the client needs to print a smaller PDF page on a bigger page size. For instance, A5 page to be printed on an A4 sheet without scaling the content.

Handle the cases when the page is rendered slowly and the document appears empty

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

Currently, when printing landscape pages the content is rotated clockwise. There has to be an option to set it to anti-clockwise.

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

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

Currently, the disabling of the scrolling functionalities in PdfViewer is pretty tricky. Expose an API that allows users to control this functionality easier (hiding the scroll bars, disabling horizontal and/or vertical scrolling).

A sample of how the scrolling could be completely disabled is attached to this item.

The document will be imported with a loss of content. The reason is that ASCII85Decoder will throw an ArgumentException when the stream doesn't end with '~>'. 

Although this is invalid case according to PDF specification, other applications are handling it and the document is successfully visualized in them. We may also consider implementing workaround that handles such invalid streams.