In this case, we have GridViewCalculatorColumn. The cell value is 123, for example. Trying to edit the cell value, the RadCalculatorEditor reset the cell value to 0. 

Workaround: increase the ItemHeight

this.radDropDownList1.DropDownListElement.AutoCompleteSuggest.DropDownList.ItemHeight = 40;

The problem I'm trying to solve is that users do not know that the original document may not be what they are seeing in the viewer when there are layers.    

A property that indicates that a document has layers would allow the system to refuse to open the document.

Our application embed a RadDock element.Unfortunately, in a non-systematic way, our application crash with this stack trace: 

Our application is a 64bit application (we migrated it to NET6 using Telerik 2022.2.510.60). As I told unfortunately in this case I'm not able to isolate the case in a simple project (as I'm used to to).

It would be useful by your side, however, make a check to the last trace line of the log I've gave to you: 

 at Telerik.WinControls.UI.ThemedFormBehavior.OnWMNCHitTest(Message& m)

If I decompile your code I find this:

L_param, returned in (1) is an IntPtr that, on a 64bit machine running a 64bit application could contains a value that SOMETIMES will crash in (2) where you try to convert it with an IntTo32 method...

99 time to 100 the code in line 755 works fine but I think that it is not guaranteed that L_Param returned in (1) can be fit in a 32bit box. This could explain why I use the phrase "...in a very random way" and why, at the moment, I'm not be able to give you a simple application where the problem is systematic.

I suspect that at line 755 we have got a problem, I'll appreciate your point of view about it.

InvalidCastException when loading a document that contains shapes with custom geometry.

In this case, we have a longer text on a single line. When the text goes outside of the view area, a horizontal scroll will appear. When we click at the begging of the line and scroll to the end of the line, clicking at the end of the text line will not change the caret position, thus we can't see the caret.

Request a JSON tagger for the SyntaxEditor

Call stack:

Telerik.WinControls.GridView.dll!Telerik.WinControls.UI.GridGroupHeaderRowElement.Initialize(Telerik.WinControls.UI.GridViewRowInfo rowInfo) Line 100
	at Telerik.WinControls.UI\GridGroupHeaderRowElement.cs(100)
Telerik.WinControls.GridView.dll!Telerik.WinControls.Export.GridExportUtils.GetRowHeight(Telerik.WinControls.UI.RadGridView radGridView, Telerik.WinControls.UI.RowElementProvider rowProvider, Telerik.WinControls.UI.CellElementProvider cellProvider, Telerik.WinControls.UI.GridViewRowInfo gridViewRowInfo, bool exportVisualSettings) Line 158
	at Telerik.WinControls.Export\GridExportUtils.cs(158)
Telerik.WinControls.GridView.dll!Telerik.WinControls.Export.GridViewSpreadExport.AddRow(Telerik.WinControls.UI.GridViewRowInfo gridViewRowInfo, int rowIndex) Line 960

This only happens initially when you first start checking/unchecking rows. See the attached gif file.

Run the attached project on a monitor with 100% DPI scaling and open the Excel-like filter popup:

100%:

After moving the form to the second monitor with 150% DPI scaling, the filter popup is not OK:

150%:

The popup is smaller and smaller with each next opening (see the attached gif file) at 150%. If you decide to move back the form on the monitor with 100% DPI scaling, the filter popup is not scaled properly.

When moving between screens with different dpi the PopupOpening event should not be called.

To reproduce:

1. Run the form with RadMultiColumnCombobox on high dpi.

2. Set SelectedIndex to -1 (no value selected initially)

3. As a result, the first value get displayed in the text area.

In this particular case, the RadMultiColumnComboBoxElement is used as a custom editor inside RadPropertyGrid control. When the editor is shown it needs to be opened 3 times to correctly calculate its width. In addition, the font is scaled twice:

To reproduce the problem, we need 2 Monitors with different scaling.
Let's say that Monitor 1 has 150% Scaling and Monitor 2 has 100% (Monitor 2 is the main monitor). When starting the program and click on radbutton1, then an empty form (Toolbox) is shown. Move the Toolbox form to the other monitor and then open the RadDropDownList. The problem is that the drop-down is shown not under the control.

Please refer to the attached project.

Steps to reproduce:

1. Set ScaleFactor to 1.5
2. Run the form on 125% monitor scaling.

Clear button in the control doesn't clear numbers.

Setting the Standard Mask to "00000" allows entering Space characters (it should not allow entering space).

RadDropDownList gets focused when the DpiScaleChanged is triggered.

Run the attached sample project. When the form is moved from monitor A (100% DPI) to monitor B (150% DPI), every RadDropDownList gets the focus which leads to scrolling the container back to the top.

Load-On-Demand self-reference hierarchy provider

Set IsThreeState property to true and choose ToggleState to Indeterminate.

Office2019Dark:

Office2019Light: