The link annotations for the first page may not work if a document was previously shown in the PdfViewer.

For example, if you scroll down and then scroll up to the previous pages, they do not show any content.

The square annotation type displays a square on the page.

When in single-page-mode and navigating to a page with the same size as the current, the content is not updated unless some touch interaction occurs.

Dear,
Please add bookmarks to the pdf reader.

Best regards.

Carlos Palomino.

ArgumentException is thrown when importing document containing form fields with the same fully qualified name

implement annotations handling when RadFixedDocument is imported with PdfProcessing

I am Lazy Loading a document in a TabViewItem on the RadTabView Control. Here are the steps.

 

1. My Page opens and I am on my Main Tab.

2. The user has two Bottom Menu Options, one of them is for a view of a Document.

3. The user selects the Document Tab Option, and the I fire an Async operation that Loads a Byte Array that the PDFViewer is bound to. This loads fine. The document successfully loads in the viewer.

4. The user goes back to the Main Tab

5. The user then selects the Document Tab Option again, the Byte Array is already loaded so I do not Load it again in my ViewModel. So, I am not updating the Source Property on the PDFViewer again once it is loaded. I also tried just reloading the document with the same results.

The application just crashes. My guess is the Rendering or Re-Rendering of the Pdf Document between Tab Selections and there is someting 

 

If the document is never loaded, the app does not crash. However, once I load the document in the PDFViewer that exists on a Tab, the Application will crash if the user moves between tabs.

   Stack Trace from the Native Crash Reporting from the Application Output Window.

 

 

Example of my Binding. Very simple Byte Array Binding, and out of the box example from the QSF Code. I also tried using a Stream and it does the same thing.

 

The command does not accept an int as a parameter. It requires the parameter to be string and not to be an index, but a page number.

Implement API for adding document outline (a.k.a bookmarks).

provide an option for FitPageToWidth. The current option is to fit document to width.

When PdfViewer is located inside Popup control, it does not take its size properly.

where if in this mode, the zoom level will be changed upon the user changing the current page (via scrolling or navigating). 

Implement the ability to display the pages of a document with a different orientation.

Expose a document loaded event

Support for FileDocumentSource

A great first effort! Many thanks!
After some use I do have these suggestions:

1. When User changes LayoutMode the ZoomLevel property changed event should also be fired. I have a Numeric Textbox to adjust viewer ZoomLevel and would like to see its text update on a LayoutMode change. However when LayoutModeChanged fires the ZoomLevel has not yet changed nor does ZoomLevelChanged later fire.
2. The toolbar item for Fit to Width should be a Toggle in all cases, i.e. toggling between Fit Width and Fit Height (or Fit Page) and should be effective at all times (sometimes has no effect if LayoutMode changed to Single Page).
3. The toolbar item to toggle LayoutMode should honor an assignment of its text property.
4. I'm currently using the change in VisiblePagesCount to determine the document is visible. However a "Loaded" event might be even better.
5. I would like to release the viewer's memory of the document before closing the XAML page. An Unload command would be helpful. For now I just assign Source = null.

When User changes LayoutMode the ZoomLevel property changed event should also be fired. I have a Numeric Textbox to adjust viewer ZoomLevel and would like to see its text update on a LayoutMode change. However when LayoutModeChanged fires the ZoomLevel has not yet changed nor does ZoomLevelChanged later fire.

By specification the explicit destinations define a required page property. However, some documents contain definition for destinations with null page value, which causes an ArgumentNullException on import.