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
Dialog for inputting the password should be implemented in order to be able to decrypt the file content.
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.
Import documents that use this type of encryption. Currently, a handled NotSupportedEncryptionException is thrown while importing such a document and it cannot be opened in RadPdfViewer. Available in R1 2018 Official Release version.
The feature was implemented for Q2 2014.
Add support for importing and filling interactive forms. Interactive Forms content is visualized read-only in RadPdfViewer UI with R1 2017 Release Available in R3 2017 Official Release Version.
As a <role> I want <ability> so that <benefit>.
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.
In Adobe and Foxit readers, the user can draw different shapes, which are later saved as images in the document.
This would allow switching the focus between form field controls by using the Tab key.
When this feature is implemented it should visualize the bookmarks similarly to in the attached screenshot. Available in R3 2018 Official Release Version.
Create appropriate methods, properties and events that will allow to users to scroll the RadPdfViewer and handle the scrolling events. Introduce API that will allow to manipulate the scroll bars.
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.