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

Incorrect or missing accessible object names in the Inspect.exe tool (MSAA).

 

 

 

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. 

Auto-complete items overlap in the VisualStudio2022 theme:

Workaround: increase the ItemHeight

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

The calendar drop-down is displayed incorrectly the first time. If I close and reopen it, it shows the entire calendar and everything is well.

Add support for data annotations.

In this particular case, the control is bound to a custom object using SchedulerBindingSource. As demonstrated in the Binding to Business Objects help article. While using this set-up, deleting Recurrence does not delete the Exceptions collection in the business object. The exceptions collection property of the Appointment inside the RadScheduler is cleared, however, the changes are not transferred to the data object.

Add support for UI Automation in RadTextBox control.

Add support for UI Automation in RadListView control.

Add support for UI Automation in RadCheckedListBox control.

Add support for UI Automation in RadSpinEditor control.

Add support for UI Automation in RadButton control.

Add support for UI Automation in RadDateTimePicker control.

Add support for UI Automation in RadMaskedEditBox control.

Add support for UI Automation in RadRadioButton control.

 Add support for UI Automation in RadCheckBox control.

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.