RadPdfViewer partially supports CCITTFaxDecode (that is basically TIFF). There are some limitations that are not supported at this stage like EncodedByteAlign = true or Group 3, 2-D encoding.
Bitonal image scaling algorithms which improve the readability of bitonal, black and white images. Due to the lack of colors within the palette of 1-bit black and white images, they become splotchy and distorted when zoomed in or out
They are used by the page and the XObjects drawn on it and deal with the overlaying of the colors. These groups are described on page 556 of PdfReference 1.7.
Dialog for inputting the password should be implemented in order to be able to decrypt the file content.
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.
As a <role> I want <ability> so that <benefit>.
A rubber stamp annotation displays text or graphics intended to look as if they were stamped on the page with a rubber stamp. When opened, it displays a pop-up window containing the text of the associated note.
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.
Most PDF viewers have option (enabled by default) which allows fields to be highlighted with colors predefined in the settings. Required fields are highlighted using different color. For example: In Adobe Acrobat Reader DC this is enabled in "Edit" -> "Preferences" -> "Forms" -> "Highlight Color" -> "Show border hover color for fields".
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.
This would allow switching the focus between form field controls by using the Tab key.
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
Layers represent groups of optional content which can be hidden or shown.
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.
This may allow someone to notify the users.
Currently, when printing landscape pages the content is rotated clockwise. There has to be an option to set it to anti-clockwise.
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!
Represents Highlights PDF content. While the other annotations are drawn on top of the content, the highlight annotation is behind the text it highlights. In other words, it has to be inserted at a specific place in the ContentElementsUILayer. The precise place where the highlight should be placed is described in the PDF file with the BDC, MCID and EMC operators. At the moment, we have implemented a read-only rendering for all annotation types which draws the annotions separately from the page content. In the case of Highlight, the annotation is drawn below the other content. With this implementation, depending on the PDF content, the highlight annotation might be visible or it might not be because in some cases there is geometry content below the highlighted text which hides the highlight annotation appearance.