Hi, all. I am using the example you guys provide in your website and you can get from here: https://www.telerik.com/blogs/winforms-scaling-at-large-dpi-settings-is-it-even-possible-#example

As you can see in the image, I open the form in my main screen with Scale 100%. I have a second screen running in 150%. When I grab the form near to the left edge side of it, it resizes in one way, what I believe that is the correct way. However, if you grab the form near to right edge side, near the minimize, maximize and close button, it resizes differently. We have several users using our application and we are not able to fix this scalling issue, even in your own example. Could you guys have a look at it and prioritize? This kind of issue has been around for a long time without a final resolution. if not possible, let us know that we will have to decide move to another development tool.

Telerik version: 2024.2.514

When I use the new project wizard provided by Microsoft for a new windows forms project it lets me select the target .net version

When I do the same with the Telerik wizard, it does not let me choose what .net Version I'm targeting and does not generate the optimal code for the target version. For example when I target .net 9.0 with high dpi support, it should generate API calls for High DPI, not an entry in the app manifest. IMHO the generated code should be as close to the Microsoft Standard for the targeted .net version as possible. 

This bug is about a mismatch between what behaviour is expected (on a functional level) and the actual behavior. There are different scenario's:

A normal example without a bug

int index = myRadGridView.Rows.Add(1, 2, 3); 

Actual and expected behavior

Adds a row to the grid, filling cells with the values 1, 2 and 3. Even when there are more columns than values, only the first 3 cells are filled.

Bug #1

int index = myRadGridView.Rows.Add(); // Will result in: myRadGridView.Rows.Add(new object[0]);

Actual behavior

IndexOutOfRangeException is thrown.

int index = myRadGridView.Rows.Add((object[])null);

int index = myRadGridView.Rows.Add(new GridViewDataRowInfo(...), new GridViewDataRowInfo(...));

// or

int index = myRadGridView.Rows.Add(new object[] { new GridViewDataRowInfo(...), new GridViewDataRowInfo(...) });

Repro-steps:

myRadGridView.Rows.Add((GridViewDataRowInfo)null);

Actual behavior

1. NullReferenceException is thrown
2. A new row is added.

Excepted behavior

1. Or an ArgumentNullException is thrown, and no rows are added.
2. Or a new row is added, and no exception is thrown.

Remark

The method AddRange is also impacted by this bug.

Repro-steps

1. Create a RadGridView
2. Add a GridViewDecimalColumn
3. Add a GridViewSummaryRowItem with a GridViewSummaryItem which:
   1. calculates the average of the values in the decimal column
   2. formats the value to two decimals after the decimal point: {0:0.00}
4. Make an event handler for ViewCellFormatting.
5. Add some rows with values to the grid.
6. In the event handler, try to read ((GridSummaryCellElement)e.CellElement).Value.

Actual behavior

The value contains a string representing the formatted and rounded value of the average of all values.

Expected behavior

The value contains a raw, not rounded,  not formatted, decimal value. 

Remarks

I expect this behavior since GridSummaryCellElement has two properties: Text and Value.
I expect those to have difference functions. Value to hold the actual calculated value, and Text to hold the formatted, round string-equivalent.

Another reason why I expect this, is that Value is of type object, not of type string. So expect a value corresponding to the original datatype of the column and/or the result of the calculation.

Follow-up questions

1. In what scenario may I expect in Value another data type that string?
2. How, during the event handler, can I retrieve the original calculated value (with using parsing, since that is slow and does not contain all the digits).

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.

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

It will be nice if one can add his custom sub menu items at design-time through the 'Add new item' menu. This was supported in the past, but the support was removed together with the introduced design-time optimizations.

Themes are applied partially to RadSpellChecker's forms.

Exception is thrown, when best fit columns is performed over a column with equal MaxWidth and MinWidth property values.

FIX.Radbutton -throws exception In design time when add image in ICO format c

Application button is overlapping the first tab when the theme is "Office2007Black".

CAB Enabling Kit - there is no way to show again smartpart that is already closed into RadDockWorkSpace.

Workaround:

         protected override void OnDockWindowClosing(DockWindowCancelEventArgs e)
        {
            if (!notifications[Suspend_Close] && e.NewWindow.Controls.Count > 0)
            {
                this.composer.SetActiveSmartPart(null);
                WorkspaceCancelEventArgs args = new WorkspaceCancelEventArgs(e.NewWindow.Controls[0]);
                OnSmartPartClosing(args);
                e.Cancel = args.Cancel;
                e.NewWindow.CloseAction = DockWindowCloseAction.Hide;
            }
            base.OnDockWindowClosing(e);
        }

        protected virtual void OnActivate(Control smartPart)
        {
            notifications[Suspend_Activated] = true;
            DockWindow dockWindow = GetSmartPart(smartPart);
            if (dockWindow != null && this.ActiveWindow != dockWindow)
            {
                dockWindow.Show();
                this.ActivateWindow(dockWindow);
            }

            notifications[Suspend_Activated] = false;
        }

When the Visual Style Builder is opened from the Smart Tag menu, VS loses focus. If you open it and close it after that you will see that the focus is not in the Visual Studio anymore.