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.
Vertical lines with small length and big thickness are drawn as short horizontal lines with big StrokeThickess. This results in rendering them as big squares, which can hide parts of the content.
Some colors are changed due to incorrect import of some graphic state colors.
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.
When an image is actually consisting of vertical sequence of smaller images, sometimes white horizontal lines appear between the smaller images.
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.
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.
When there is no ToUnicode CMap, the text from the Simple Font instance should be extracted by mapping the glyph name to its corresponding charcode according to Adobe Glyph List. Additionally, the Differences array should be included in these calculations when there is custom encoding. The current implementation of RadPdfViewer makes ToString to the original char id byte value which leads to wrong characters.
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.
Currently, we have reproduced this issue with fonts AmnestyTradeGothic, OfficinaSanITC and OfficinaSanITC-Book.
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.
The issue is reproducible only for some specific font files. The characters are displayed as rectangles. This seems to caused by incorrect glyph name and glyph id mapping.
Some of the lines that should be dashed are rendered as continuous lines.