The used cell range is expanded when styles to all columns are applied and one copies an entire row.
Workaround:private void RadSpreadsheet_WorkbookChanged(object sender, EventArgs e)
- Select some cells within the same column using Ctrl+Click
- Use the context menu to copy the cells
This works in Excel when the cells are within the same column.
Exception when exporting document that contains links with an empty address.
Workaround:private void Button_Click_1(object sender, RoutedEventArgs e)
- Set the language to Korean
- Type "r" in one of the cells
- Use the AutoFill functionality
At this point, FatalExecutionEngineError occurs (see attached).
At the moment the print settings set to the WorksheetPageSetup class are not passed to the Print dialog which leads to bad user experience. If you set the print settings of the RadSpreadsheet like so: WorksheetPageSetup pageSetup = this.radSpreadsheet.Workbook.ActiveWorksheet.WorksheetPageSetup; pageSetup.PageOrientation = PageOrientation.Landscape; and then select Print, the Spreadsheet print menu will show the print preview as landscape. However, when after that you click on Print for the default print dialog to appear and then click Preferences, you will notice that the preference is set to Portrait. The print job will be Landscape, but the incorrect information in the default dialog creates confusion. This is an example of how to set the preference of the default dialog: PrintDialog printDialog = new PrintDialog(); var printTicket = printDialog.PrintTicket; printTicket.PageOrientation = System.Printing.PageOrientation.Landscape;
At the moment when any of the properties are changed, e.g. the frozen panes, the UI is not notified and you have to export and import the file in order for the UI to pick them up. Workaround: There are several workarounds: 1. Change the active worksheet and return to the old one 2. Export and import the document 3. Change the workbook of the RadSpreadsheet to a new one, and return the old one after that
We should provide an easier API allowing the customers to remove the key bindings or change the commands that they trigger. Workaround: There is attached a sample showing how all the commands triggered by the key bindings can be disabled.
If plain text is pasted in a cell, and the text is automatically recognizable as date, number, percentage, formula or other format, the text is always converted to the recognized number format. Instead, the cell's current number format should affect the convertion in the following way: - If the current format is General -> parse the value with the automatically recognized format, and set the value with the automatically recognized format - If the current format is Text -> set the value as text, and preserve the current format (Text) - If the current format is any other format -> try parse the value with the current format - Successful -> set the parsed value with the current format - Unsuccessful -> parse the value with the automatically recognized format, and set the parsed value with the current format. As a result, strings which are recognizable as dates, for example, are pasted as their numeric representation instead of with their Date formatting. Also it's not possible to paste something as plain text. Workaround: for always pasting plain text: Create custom Paste button and executes the following code: this.radSpreadsheet.ActiveWorksheetEditor.Selection.Cells.SetValueAsText(Clipboard.GetText());
When setting the following strings as cell value, they are recognized as dates. In industry standard applications like MS Excel and OpenOffice, they are recognized as strings: - "12 3456" in bg-BG, fr-FR, ru-RU, sv-FI, en-US - "12.3456" in de-DE - "1 23" in en-US - "2013/5" in en-US - "3000-03" in en-US
When RadSpreadsheet is placed inside a data template and the Workbook property is bound, the binding fails. In the Convert() method of the debug converter, the proper value is set. However, an empty workbook is displayed in the view.
The overlapping of SelectionFill and SelectionStroke geometries may be seen in the attached screenshot. This scenario may be reproduced with the following RadSpreadsheet instance: <telerik:RadSpreadsheet SelectionStroke="Red" SelectionStrokeThickness="10" FillHandleSelectionStroke="Green" SelectionFill="#550000FF" />
The visualization and scrolling of documents containing many merged cells (e.g. 1000) is very slow. The control becomes almost unusable when the number increases.