When applying a ListDataValidation, the created RadDropDownButton, which has a RadPathButton in it, looks broken when using the Windows11, Office2013, Office2019, and VisualStudio2019 themes.

Check how the performance can be improved in this scenario. The StyleGallery is taking much time to load, the GetUsedCellRange method is called multiple times.

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;
    }
}

The horizontal ScrollBar of RadSpreadsheet is missing the bottom border of its track. Additional to that there is a slight offset between the right end of the viewport and the right button of the ScrollBar.

To work this around, set the Margin of the horizontal ScrollBar to 0, and modify its ControlTemplate so that it adds a bottom border for the track's RepeatButton elements.

private void RadSpreadsheet_Loaded(object sender, RoutedEventArgs e)
{
    var spreadsheet = (RadSpreadsheet)sender;
    var scrollBar = spreadsheet.ChildrenOfType<ScrollBar>().FirstOrDefault(x => x.Name == "HorizontalScrollBar");
    scrollBar.Margin = new Thickness(0);
    scrollBar.Template = (ControlTemplate)this.Resources["MyCustomScrollBarTemplate"];
}

Improve the load time when the ribbon UI is used.

For the German language translations, the following resource keys are translated into Dutch instead:

• Spreadsheet_PrintPreview_FitSheetOnOnePage
• Spreadsheet_PrintPreview_FitSheetOnOnePage_Description
• Spreadsheet_PrintPreview_FitColumnsOnOnePage
• Spreadsheet_PrintPreview_FitColumnsOnOnePage_Description
• Spreadsheet_PrintPreview_FitRowsOnOnePage
• Spreadsheet_PrintPreview_FitRowsOnOnePage_Description

The numeric box that allows you to select the "to" page in the PrintPreviewControl is clipped when the "Pages:" and "to" strings are translated to a language where these words are longer. For example, this reproduces with Dutch culture which uses the "Pagina's:" and "naar" texts.

To work this around, you can get the Grid panel that hosts the content and increase the Width of one of its ColumnDefinitions.

  private void PrintPreviewControl_Loaded(object sender, RoutedEventArgs e)
  {
      var printPreview = (PrintPreviewControl)sender;
      var rootGrid = printPreview.FindChildByType<Grid>();
      rootGrid.ColumnDefinitions[0].Width = new GridLength(355);
  }

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.

Copy/Paste a shape and then an image leads to a wrong result. 

Steps to reproduce: 

We have a problem creating an Excel file with Telerik.Windows.Documents.Spreadsheet. 
In our last release for our customers we used Telerik WPF version 22.2.613.40 (Spreadsheet DLL)

When calling the following line of code

m_Worksheet.Cells[m_CurrentRowIndex, m_CurrentColumnIndex].SetValue("111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111 111111111111111111111111111111111111111111111111111111111111111111111 111111111111111111111111111111111111111111111111111111111111111111111 111111111111111111111111111111111111111111111111111111111111111111111 111111111111111111111111111111111111111111111111111111111111111111111 111111111111111111111111111111111111");

the CellValueType is set to text and the Value is correct.

We have now switched our project to .NET 7 and Telerik WPF to version 2023.2.519.70.

We discovered that this line of code no longer works.

The CellValueType is now Number and the Value Infinity

Have you changed anything internally? How can we solve the problem now?