The CustomFilterDialogContent element's OK and Cancel buttons are different in size for the Windows 11 theme.

To work this around, you can subscribe to the Loaded event of the CustomFilterDialogContent element and retrieve the RadButton with x:Name="PART_ButtonCancel" via the ChildrenOfType extension method. On the retrieved button, set the VerticalAlignment property to Center.

The following code snippet showcases this suggestion's implementation:

static MainWindow()
{
    EventManager.RegisterClassHandler(typeof(CustomFilterDialogContent), LoadedEvent, new RoutedEventHandler(OnCustomFilterDialogContentLoaded));
}

private static void OnCustomFilterDialogContentLoaded(object sender, RoutedEventArgs e)
{
    RadButton cancelButton = ((CustomFilterDialogContent)sender).ChildrenOfType<RadButton>().FirstOrDefault(x => x.Name == "PART_ButtonCancel");

    if (cancelButton != null)
    {
        cancelButton.VerticalAlignment = VerticalAlignment.Center;
    }
}

Handle the case when the cell is too small and the value contains a decimal separator. 

For example, see attached images. 

When filter is added to merged cells, there should be a single filter icon displayed in the combined cell. Instead, multiple filters appear - one for each column in the range of the merged cells.

Hi Team,

   I have backported the Xlsx file to Xls format. When I am trying to import the backported file using the Radspreadsheet UI control, I find that it has lost the color formatting which was existing in the original Xlsx file. Where as when we open the back ported file with Excel application we find that all the data and formatting is maintained.

So the request is that after backporting  and while importing the file, it should not loose the minimal xls supported features which Excel is able to support.





Attached is the InitialFile.xlsx and BackPorted.xls file

Note that Xlsx file if imported it maintains the data and formatting information of the workbbok when loaded via UI control.
Let us know in case of any more details or queries.

Exepct this to work

Regards,

Manish.

We have a document in XLS format produced by GemBox. The yellow cells get black once the document is imported and then exported (back to XLS or XLSX) with RadSpreadProcessing.

#.##0,00;-#.##0,00;;@ does not work in RadSpreadsheet. It should suppress visualizing of ) values.

Workaround: #.##0,00;-#.##0,00; ;@ works fine (there is ' ' [space] set for the zero values).

Wrong exception messages are constructed sometimes, due to problem in the internal Guard.ThrowExceptionIfTrue and Guard.ThrowExceptionIfFalse methods:

- Guard.ThrowExceptionIfTrue throws InvalidOperationException with text "<paramName> should be true.", instead the text should be "<paramName> should be false."

- Guard.ThrowExceptionIfFalse throws InvalidOperationException with text "<paramName> should be false.", instead the text should be "<paramName> should be true."

Available in LIB Version 2017.2.828.

When in a cell is inserted text with leading spaces, they are ignored when export and Excel doesn't show them.

The fix will be available in our latest LIB release (v. 2015.1.0323).

The fix is available in our latest LIB release (v. 2015.1.0323).

The fix will be available in our official release 2015 Q2..

This item is declined. The visualized border describes the print area.

When a cell's format is set to "Percentage" and then a number is entered, the number's format is incorrect. For example, if "10" is entered in such a cell, the value is visualized as "1000.00%", instead of "10.00%".

Can we have the ability to hide the cell selector rectangle in the RadSpreadsheet? If we had this, along with the current existing functionality we would have spreadsheet capabilities inside what looks like an 'empty' page. It would be good for reporting purposes where the developer can make full use of the spreadsheet's functions but completely hide the 'spreadsheet look-and-feel' from the user.

The fix will be available in our next LIB release (v. 2015.03.1005).

Currently, only Workbook/Worksheet could be protected. Would be nice to expose a way to protect cells for scenarios in which only particular cells should be locked for modifications.

The item is duplicated. Please, find the approved public item at http://feedback.telerik.com/Project/143/Feedback/Details/145412

Add support for preserving and exporting the macros in a macro-enabled workbook.

When using the OpenFile command to open a document, you should be able to obtain the Name of the workbook in the WorkbookChanged event handler.