Currently, this could be achieved by exporting the document to PDF and then by using RadPdfViewer's WPF control ThumbnailFactory class. Sample code may be seen at this forum post: http://www.telerik.com/forums/pdf-thumbnail-returns-transparent-images#jO33X-E8Cki_qLh_KsToWg Help article: WPF PdfViewer - Exporting Fixed Page to Image - Telerik UI for WPF

Add an option to save or load a custom created DocumentTheme.

Currently, this could be achieved this way:

Setting SetIsBold method to true on a CellSelection, resets the font size of those cells to 11 points.
See the generated file of the attached program.
Cells C1:F1 have font size 11 instead of expected 9.

 

PS: Is it really necessary to have a support plan to report bugs?

The colors of the charts are determined by the theme in the default scenario. However, customers can apply any color to the series and the legend respectively. In such cases, RadSpreadProcessing doesn't import the custom colors and uses the ones defined by the theme.

The columns of the sheet are split when exporting to PDF.

Wrong measured column width when exporting to PDF after binaries version 2019.2.624.

One should be able to set the axis titles in the code. The attached images show an example of the exported document opened in Excel. 

Add support for MID function. MID returns a specific number of characters from a text string, starting at the position you specify, based on the number of characters you specify.

MID(text, start_num, num_chars)

A list of the supported functions is available at http://docs.telerik.com/devtools/document-processing/libraries/radspreadprocessing/features/formulas/functions

This function can be implemented as a custom function. Check the following resources for more details on how to achieve that:

- http://docs.telerik.com/devtools/document-processing/libraries/radspreadprocessing/features/formulas/custom-functions
- https://github.com/telerik/xaml-sdk/tree/master/Spreadsheet/WPF/CustomFunctions

Add support for the Data Labels in the chart (see attached).

The exception is thrown when importing a document that contains a not supported BuiltInNumberFormat.

While importing the arguments of the data validation rule, the formula is treated as text and its separators are replaced with the list separator defined in the current culture. This leads to an invalid formula treated as a list of strings.

Currently, the worksheet of the shape and the collection it belongs to should be the same. Make it possible for the ChartShape and the data source to be on different worksheets.

Currently, row/column groups cannot be collapsed/expanded through the public API. User should be able to specify row's/column's "collapsed" attribute indicating whether the outlining is in a collapsed state.

Removing/adding rows/columns inside a worksheet requires all the data after them to be translated according to the change. This operation is slow and affects editing performance.

Currently, the chart lines support only solid fill for their outlines.

The API should be able to provide a way to move the X-axis away from the 0 value on the Y-axis or to the bottom of the chart when there are negative Y-axis values.

In Excel this can be achieved by right click on the axis, then from the context menu select "Format Axis".  Go to the "Labels" group and then in the "Label position" field select the desired value.

The COUNTIFS function returns the count of cells that meet one or more criteria.

The data validation rule should have values for formula1 and formula2 elements, which define the start and end values for a range to validate between. When such values are missing, a NullReferenceException is thrown on import and the document cannot be imported.

Details:

Sometimes the customers need to obtain the result of a formula without adding it as a value to a specific cell.