Add support for Trigger Events

Is there a way to customize the box to request a signature?

 

 

Thanks in advance

A dictionary specifying any resources (such as fonts and images) required by the form XObject (see Section 3.7 from http://partners.adobe.com/public/developer/en/pdf/PDFReference.pdf

Show the DropDownList icon when the document contains ComboBox field. This is the default behavior in adobe as well. 

The CID font may define a description of the glyph widths. By specification, the widths can be defined in two ways - with start and end CID codes or with and an array of CID codes. However, the current implementation supports only CID arrays as direct property and not as an indirect object. This leads to incorrectly imported glyph widths and text positioning issues.

When importing document with text containing char code mapped to .notdef glyph name an ArgumentException: 'The encoding is not supported.' is thrown.

I am using RadPDFViewer, i built a specific toolbar for manage the funcionalities of the viewer.

I didn´t found the any event when the current page is changed in viewer. I would like to show a label "Page NN of TT".

 I found this "https://www.telerik.com/forums/page-changed-detected", but didn´t have this event in RadPDFViewer.

 

Whats the better solution for the raise event when the current page displayed is changed? 

 

Can you help me ?!? 

When saving Form Fields in document defined with linearized PDF structure, it produces a document that fails to open in Edge.

Implement the import of documents containing Type 3 fonts.

Hi

I'm using PDFViewer to display several documents in my application. Most of them are shown the right way, but there are others that appear "empty", or with some graphic elements but no text. I can see them perfectly with external third party viewers.

I've just downloaded and installed 2019.3.1022, but this issue remains.

I send some samples of PDF that are not showing.

Thank you in advance for your help.

I would like to be able to set a list of page numbers that will be skipped/not loaded by the PDFViewer.

To reproduce:

  doc.Pages[0].CropBox = new Rect(150, 150, doc.Pages[0].Size.Width - 30, doc.Pages[0].Size.Height - 30);

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.

When a pdf/a compliant document is opened in Adobe, there is a bar saying that the document is compliant with the standard. Expose such functionality in PdfViewer as well.

The current implementation relies on valid cross-reference table offsets in the PDF documents so that PDF objects are easily found and parsed. However, a mechanism for importing documents with invalid cross-reference table offsets may be implemented.

The attached project shows how to repair such documents.

When importing a document with empty pages collection an ArgumentNullException: 'Value cannot be null.
Parameter name: page', is thrown, which leads to application crash.

I am using the PDFViewer control in a VisualStudio VB.NET application. The PDF is not showing all the details as it appears in Adobe PDF Reader. In particular, the text is not showing up (but is highlighted when selected) and there is gray shading that is not visible. See attached sample file. Please advise.

Please refer to the attached gif file and sample project. When you hide the overflow button with the first pixel, although it is indicated as Visible, it is actually not shown.

Workaround: Timer timer = new Timer();

private void commandBarStrip_ItemOverflowed(object sender, EventArgs e)
{
    timer.Interval = 100;
    timer.Tick += timer_Tick;
    timer.Start();

}

private void timer_Tick(object sender, EventArgs e)
{
    timer.Tick -= timer_Tick;
    var commandBarStrip = this.radPdfViewerNavigator1.CommandBarElement.Rows[0].Strips[0];
    commandBarStrip.OverflowButton.Visibility = ElementVisibility.Visible;
    timer.Stop();
}

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.