This is reproducible when the matched result resides on different page.
Workaround: You may subscribe to the RadFixedDocument.CaretPosition.PositionChanged event and implement the scroll logic. Subscribe to PdfViewer's DocumentChanged event first if the document is not loaded.
private void CaretPosition_PositionChanged(object sender, EventArgs e)
{
Telerik.Windows.Documents.Fixed.Model.RadFixedPage currentPage = this.pdfViewer.Document.CaretPosition.Page;
int pageIndex = this.pdfViewer.Document.Pages.IndexOf(currentPage);
this.pdfViewer.GoToPage(pageIndex + 1);
}
Currently, we use System.Windows.Controls.TextBox for editing both TextBox and CombTextBox field types. We should implement CombTextBox editor which would allow having spaces between characters during the editing process.
This action is usually linked to a Button field and with it, the user of the application may revert all field values to their defaults.
Expose a button in the UI that can be used instead of Ctrl+F. Such a button can be currently added by customizing the default toolbar. For more information, check the documentation that describes how to achieve that: https://docs.telerik.com/devtools/wpf/controls/radpdfviewer/default-ui#customizing-the-default-ui
This is reproducible when the field VariableTextProperties has zero value for font size. Fix available in LIB Version 2018.1.402.
An ArgumentException is thrown internally as the font name is null. However, the name is defined in the base font and can be obtained from it. Fix available in LIB Version 2018.1.402.
Currently, RadPdfViewer uses default constant value for the font size in this scenario.
The file contains the following: 68.637 604.561 455.981 -107.996 re 72.237 604.561 l S Instead of the more usual 68.637 604.561 455.981 -107.996 re S 72.237 604.561 l S Both are valid but the first seems to create a problem. Fix available in LIB Version 2018.1.319.
The exception is thrown when the RadioButtonField options array contains nested arrays instead of string values. Fix available in LIB Version 2018.1.312.
When a PDF is printed all images are omitted. Available in R1 2018 SP1 version.
At the moment the theme of the RadPdfViewerToolBar can be set only by setting the theme of the entire application. The individual setting (using telerik:StyleManager.Theme="Windows8") should also be supported.
Setting Handle property to false should result in rethrowing the exception and interrupting current RadFixedDocument rendering. This is related to Exception Handling Mechanism mentioned in this documentation article: https://docs.telerik.com/devtools/wpf/controls/radpdfviewer/document-model/exceptionhandling
Loading page with a lot of text takes several minutes which is unacceptable. This performance issue is caused by class GlypInfoFactory, which caches the glyph information. Available in LIB Version 2017.3.1225.
Enable the customers to directly save the document inside PdfViewer to a file or a stream. Available in LIB Version 2017.3.1225.
The Ã’ symbol is not found in the encoding as is rendered as a ".notdef" glyph. Available in LIB Version 2017.3.1127.
Decode array for image masks with DeviceGray color space is not respected, and always the default array of [0 1] is used for visualization. When the mask is encoded with [1 0], the mask is applied inversed, making the wrong pixels transparent. This may lead to images becoming invisible. Fix available in LIB Version 2017.3.1120.
This may result in inversed transparency issue when rendering images with ImageMask. Fix available in LIB Version 2017.3.1120.
Currently, the implementation relies on the fact that the previous cross-reference value of a stream object is always a stream object. Instead during the cross-reference recursion, we should check on each step whether the previous cross-reference item is table or stream. Fix available in LIB Version 2017.3.1120.
Before starting to decode big image, try to estimate the needed memory and check if such memory is available using the MemoryFailPoint class. The behavior in case of failure in printing scenarios should be considered carefully. The user should be able to turn the behavior on and off.
Currently, the Find() method searches from the beginning of the document to its end. Enable the customer to specify a particular range of pages the method should search through.