When trying to open the QuickStart solution from 

C:\Program Files (x86)\Progress\Telerik UI for WinForms 2025 Q1\Examples

installation folder, the following error appears:

In this scenario, we have custom RadListFilterPopup. There could be a scenario in which we don't need the default menu items( input textbox, list of distinct values, buttons). If we override the CreateListFilterMenuItems() method and don't call the base code, NullReferenceException will be thrown in the Dispose() method.

In the current scenario, when clicking on the checkbox inside a GridViewCheckBoxColumn, the CellBeginEdit event will be called. If we cancel the event by setting the Cancel property to true, the CellBeginEdit will be called twice.

ImageKey is cleared when moving a node from one treeview to another and disposing the first.

After a hyperlink is edited in a RTF document it duplicated

Visual Studio 2022 crashes when working with a solution containing two WinForms projects:

• Project 1: WinForms (.NET 9) with Telerik
• Project 2: WinForms (.NET 6) without Telerik

Steps to Reproduce:

1. Create a new solution in Visual Studio 2022.
2. Add two WinForms projects:
   • Project 1: WinForms (.NET 9) with Telerik
   • Project 2: WinForms (.NET 6) without Telerik
3. Open the WinForms designer for a form in Project 1 (Telerik, .NET 9).
4. Without closing the designer, open the WinForms designer for a form in Project 2 (.NET 6, no Telerik).
5. Switch to the code view of the form in Project 2.
6. Switch back to the WinForms designer in Project 2.

Expected Result:
Visual Studio should smoothly switch between code and designer views without issues.

Actual Result:
Visual Studio freezes and crashes after switching back to the WinForms designer in Project 2.

Environment:

• Visual Studio 2022
• Windows Version: (Windows 11 x64)
• Telerik WinForms Version: (2025.1.211)

Additional Notes:

• The issue seems to be related to handling different .NET versions and Telerik components in the same solution.
• The crash occurs consistently when following the steps above.
• No explicit error messages are shown before Visual Studio closes.

---

When the RadPropertyGrid is in group scenario and we expand more property items, the scroll value is incorrect. 

 

The control allows you to scroll the view while dragging and appointment. In a case when the appointment is at the bottom of the view and we try to move it above, the view will scroll to see the top cells. When the mouse is above the column header cells, the scroll stops. This could be improved.

Workaround: set UseCompatibleTextRendering to true.

In this case, we have a GridViewHyperlinkColumn in which we have a cell with an empty string or null value. Exporting the control in XLSX format leads to an exception.

In this scenario, the MultiSelect option of the control is enabled. If we click and hold the mouse to select multiple cells and go over a merged cell, NullReferenceException is thrown.

The EnableHotTracking property works only in the first level hierarchy. The lower levels still get highlighted.

In the following scenario, we have enabled the pager functionality of the control. If we move to a different page and then set the DataSource to Null, the page index will not be reset. 

How to reproduce: set the Size property of the form in the designer of Visual Studio, pay attention to the serialized ClientSize value. Run the form and check the ClientSize, it has increased

Workaround: 
public partial class Form2 : RadForm
{
    public Form2()
    {
        InitializeComponent();
        Padding p = TelerikDpiHelper.ScalePadding(this.FormBehavior.ClientMargin, new SizeF(1f / this.RootElement.DpiScaleFactor.Width, 1f / this.RootElement.DpiScaleFactor.Height));
        this.MaximumSize = new Size(this.Size.Width - p.Horizontal, this.Size.Height - p.Vertical- this.FormBehavior.ClientMargin.Bottom + this.FormElement.TitleBar.Size.Height);
    }

    protected override void OnShown(EventArgs e)
    {
        base.OnShown(e);

        this.MaximumSize = new Size(0, 0);
    }
}

To reproduce:
- Set the StartPosition to CenterScreen
- Show the form on a HDPI monitor

Workaround:
var form = new RadForm();

float dpiX, dpiY;
Graphics graphics = this.CreateGraphics();
dpiX = graphics.DpiX /100;
dpiY = graphics.DpiY /100;

form.StartPosition = FormStartPosition.Manual;
var monSize = Screen.FromControl(this).Bounds;
var centerX = (monSize.Width / 2) - (form.DesktopBounds.Width * dpiX / 2);
var centerY = (monSize.Height / 2) - (form.DesktopBounds.Height * dpiY/ 2);
form.Location = new Point((int)centerX,(int) centerY);
form.Show();

Create build-in Google Map provider.

Good morning,

when I open a mdi child form from another child form and change WindowState from Minimize to Normal the form is not shown with correct size.

Hello team!

I've found a misbehavior on RadForm when setting the size.

When you set the Size of the Form before it actually has shown then it will do some re-calculation, change the form size several times, and ending up in a too big size. The behavior is different to a original Form and that's why I'd treat this as bug.

The first screenshot shows a RadForm that set itself to ClientSize = 500; 500 on the constructor, like usual. It ends up in a size slightly bigger then defined.


This second screenshot shows a RadForm that set itself to ClientSize on "Shown". It ends up in having the correct size.

Whenever you set a breakpoint to the method "Form1_Resize" you can capture that the first time the Size of the RadForm get changed is our "ClientSize = new Size(500, 500)". Then the Size get changed two times by RadForm itself to something slightly smaller. Lastly the Size get changed by RadForm another time, but this time slightly bigger

This behaviors can lead to inconsistent UI size, e. .g small spaces when using AutoSize = true in certain cases. But yet didn't figured completely out when exactly it happens, just that it comes from this slightly increased Size of RadForm.

Can you please take a look to it and, if it is one, report it as bug?

Thank you very much!

Regards,
Pascal