Approved
Last Updated: 17 Jan 2019 07:43 by ADMIN
When the user makes the pinch gesture the expected behavior would be for the zoomed point to be the touch position, but it is instead the top left corner of the page.
Approved
Last Updated: 15 Jan 2019 15:25 by ADMIN
WPF allows running multiple UI threads in a single process. When RadPdfViewer is used in such scenarios, sometimes InvalidOperationException: 'The calling thread cannot access this object because a different thread owns it.' is thrown. 

Scenarios:
- Show Find dialog (or any other of the dialogs available for register in ExtensibilityManager class) for the first instance, the for the second instance.
Completed
Last Updated: 21 Jan 2019 08:54 by ADMIN
Hyperlinks within a document are not working via touch. They are working only when a mouse is used.
Declined
Last Updated: 28 Dec 2018 09:16 by ADMIN

The exception is thrown with the message "Password is not correct" even when the user password is correct. This issue occurs for specific encryption algorithm parameters only.

Item is declined because this functionality is not supported and has a logged feature request to support it.

Approved
Last Updated: 28 Dec 2018 09:27 by ADMIN
By specification, when some of the destination parameters have null value, the current value of that parameter is to be retained unchanged (This rule applies for most of the properties). For example, if Location (XYZ) destination is imported and any of the left, top, or zoom parameters is null, the current value of the visual viewport for the specified property should be retained. 

Workaround: Edit the document destinations and set default values. For example if the document contains Location destinations the Left, Top and Zoom properties can be set:
foreach (var annotation in document.Annotations)
{
    Link link = annotation as Link;
    if (annotation != null)
    {
        if (link.Destination is Location location)
        {
            location.Left = location.Left != null ? location.Left : 0;
            location.Top = location.Top != null ? location.Top : 0;
            location.Zoom = location.Zoom != null ? location.Zoom : 1;
        }
    }
}
Approved
Last Updated: 26 Oct 2018 13:58 by ADMIN
ADMIN
Created by: Anna
Comments: 2
Category: PDFViewer
Type: Bug Report
1
Some files when opened with PdfViewer will throw a KeyNotFoundException which will be handled. Parts of the text in the file might or might not be missing.
Completed
Last Updated: 25 Oct 2018 13:10 by ADMIN
Customers are reporting an issue when trying to copy content in an application hosted on a remote machine (there are reports using TigerVNC and Citrix).  The exception is thrown from the Clipboard class with a message: OpenClipboard failed (Exception from HRESULT: 0x800401D0 (CLIPBRD_E_CANT_OPEN)).

It seems like such a behavior could be reproduced when the clipboard is already opened by another application. Here is a discussion on the matter: https://stackoverflow.com/questions/68666/clipbrd-e-cant-open-error-when-setting-the-clipboard-from-net

Fix available in LIB Version 2018.3.1029.
Completed
Last Updated: 03 Dec 2018 12:41 by ADMIN
This might result in invisible annotations.
Approved
Last Updated: 08 Oct 2018 11:52 by ADMIN
When the file has an annotation with a destination and this destination is missing from the destinations (Dests) collection of the catalogue, KeyNotFoundException is thrown when you try to scroll to the page where the annotation is located. A better behavior would be for nothing to happen when trying to click on the annotation leading to the destination.
Approved
Last Updated: 21 Sep 2018 13:39 by Georgi
When a ToUnicode CMap is defined for Simple Font (TrueType or Type1 font) which maps font character codes to two or more Unicode character values, the extracted text should contain the whole set of characters defined in the mappings. The current implementation of RadPdfViewer takes the first character specified in the ToUnicode mapping which leads to missing characters.
Completed
Last Updated: 01 Aug 2018 12:35 by ADMIN
ADMIN
Created by: Deyan
Comments: 0
Category: PDFViewer
Type: Bug Report
1
Instead, we should not visualize them and they should not be interactable with the mouse.

Fix available in LIB Version 2018.2.730.
Completed
Last Updated: 01 Aug 2018 14:12 by ADMIN
When importing documents containing Interactive FormFields with an empty collection of Normal state appearances, a NullReferenceException is thrown, which leads to non-editable FormFields in PdfViewer.

Fix available in LIB Version 2018.2.730.
Approved
Last Updated: 23 Jul 2018 10:10 by ADMIN
It seems that the glyph outlines are rendered wrong for some specific CFF font files. For instance, the issue is reproducible with "Aleo-Light" font.
Approved
Last Updated: 15 Mar 2019 07:13 by ADMIN
When importing document containing a destination which points to invalid page reference, KeyNotFoundException is thrown.
Approved
Last Updated: 16 Jul 2018 07:47 by Georgi
When the Interactive Form Fields are in read-only mode, the user should not be able to change the value of the field. The associated Form Field widgets should not interact with the user, e.g. they should not respond to mouse clicks or change their appearance in response to mouse motions.
Approved
Last Updated: 22 Jun 2018 12:56 by Georgi
When modifying Interactive Forms TextBoxField's value the entered changes are preserved after is clicked out of the TextBoxField's editing area. However the changes are not applied when the click is performed on the save button.

As possible workaround you can raise a MouseLeftButtonDown event on the RadPdfViewer and after this execute the SaveAsCommand. For example:

private void SaveButton_Click(object sender, RoutedEventArgs e)
{
    MouseButtonEventArgs mouseEventArgs = new MouseButtonEventArgs(Mouse.PrimaryDevice, 0, MouseButton.Left)
    {
        RoutedEvent = FrameworkElement.MouseLeftButtonDownEvent
    };
 
    ((FrameworkElement)this.pdfViewer.FixedDocumentPresenter).RaiseEvent(mouseEventArgs);
    this.pdfViewer.CommandDescriptors.SaveAsCommandDescriptor.Command.Execute(null);
}
Approved
Last Updated: 19 Jun 2018 13:42 by ADMIN
When Find Next is used multiple times fast, and pages are still loaded asynchronously, sometimes NullReferenceException is thrown with the following call stack:

System.NullReferenceException: Object reference not set to an instance of an object.
   at Telerik.Windows.Documents.Fixed.Text.TextRecognizer.GetLastCharacter()
   at Telerik.Windows.Documents.Fixed.Text.TextRecognizer.IsLineBreak(Glyph glyph)
   at Telerik.Windows.Documents.Fixed.Text.TextRecognizer.ProcessGlyph(Glyph glyph)
   at Telerik.Windows.Documents.Fixed.Text.TextRecognizer.CreateTextPage(RadFixedPageInternal page)
   at Telerik.Windows.Documents.Fixed.Text.TextDocument.GetTextPage(Int32 index)
   at Telerik.Windows.Documents.Fixed.Search.KMPTextSearch.FindNext(TextDocument document, TextPosition startPosition, String searchText, Boolean matchCase, Boolean wholeWordsOnly)
   at Telerik.Windows.Documents.Fixed.Search.TextSearch.Find(String text, TextSearchOptions options)

...
Completed
Last Updated: 14 Jun 2018 13:44 by ADMIN
Usually, the entries are on neighboring rows. However, some producers introduce some extra blank rows between entries and this causes exception in RadPdfViewer implementation.

Fix available in R2 2018 SP1 release version.
Approved
Last Updated: 01 Jun 2018 12:54 by ADMIN
The issue is reproducible only on Windows XP. On newer versions of windows, the images are rendered as expected.

WORKAROUND: You may inherit DctDecode class in order to implement custom decoder. For instance, you may try calling DecodeWithJpegDecoder method from the base class as mentioned in the note of this documentation article:

http://docs.telerik.com/devtools/wpf/controls/radpdfviewer/customization-and-extensibility/customize-pdf-rendering

A sample implementation of these custom decoder may be seen below:

public class CustomDctDecode : DctDecode
{
    public override byte[] Decode(PdfObject decodedObject, byte[] inputData, DecodeParameters parms)
    {
        return DecodeWithJpegDecoder(inputData);
    }
}
Completed
Last Updated: 14 Jun 2018 14:45 by ADMIN
The width values from the widths PDF property should be taken with priority compared to the font file calculations.

Fix available in R2 2018 SP1 release version.