Documentation about High-DPI mechanisms available on the website is very outdated and mostly does not consider the changes and improvements that Microsoft made with .net 7.0 and 8.0.

What's needed is thorough documentation about Telerik's behavior in comparison with the different situations on .net Framework 4.9 and the major .net Versions 6.0, 7.0, and 8.0.

Kind regards

Erwin

Use the attached sample project.

Sceen 1 (Screen with program shortcuts) on the right in the gif: this screen has display scale 125%

Screen 2 (Screen with the Form) on the left in the gif: this screen has display scale 100%

When all three toolwindows are placed in the forms, there is no issue. The Dropdown list of ToolWindow1 (floating, dockable..) when opened is placed correctly.

If I moved the ToolWindow3 from Screen2 to Screen1 and make it the most recent active window (by clicking on it), I go back to the Screen2 and open the dropdown list of Toolwindow1, this list's position is now wrong and the text size bigger. This is because it takes the display scale (125%) of  the screen where the most recent active toolwindow (ToolWindow3 ) is.

If I popup the ToolWindow2, place it in Screen2 (the same screen with ToolWindow1), make ToolWindow2 the most recent active window, and open the dropdown list of Toolwindow1, this list's position is now correct and the text size normal. This is because it takes the display scale (100%)  of  the screen where the most recent active toolwindow (ToolWindow2 ) is.

Workaround: add app.manifest file and declare the application as DPI aware: 

I'm trying to initialize RadControlSpyForm in a .NET 2.0 application and it throws the following exception:

System.InvalidCastException: 'Unable to cast object of type 'System.Windows.Forms.SplitContainer' to type 'System.ComponentModel.ISupportInitialize'.

I did some research, and I found that since SplitContainer doesn't inherit from System.ComponentModel.ISupportInitialize until .NET 4.0, this message shows up in solutions where a project is downgraded from .NET 4.0, but the Form designer isn't regenerated to remove the SplitContainer cast to ISupportInitialize to call BeginInit() and EndInit().

It would be good to offer default localization providers for some languages like German, Spanish, French, etc.

It is possible to use the following site that Microsoft provides for this purpose: https://www.microsoft.com/en-us/language 

The writing-mode attribute is ignored when rendering RadSvgImage. 
Here is a sample SVG:

<svg width="200" height="200" viewBox="0 0 200 200" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg">
<g>
    <text style="font-size:20px;writing-mode:tb;" x="30" y="30">
        Vertical text
    </text>
    <text style="font-size:20px;writing-mode:vertical-lr;" x="50" y="50">
        Text 2
    </text>
</g>
</svg>

• Control Structure Pane - For example, RadForm has a RadTitleBarElement, which contains no styles, because they are inherited from the RadTitleBar control. Here we can add a note, which says from which control the styles are inherited:
  
• Design / Preview Pane - Click on an element from the Design view and select it into the control element tree.
• Elements Pane - Add an option to expand all sub-nodes in the Control Structure tree. Save the setting for the filter chosen by the user.
• Find repository usages: Add an option to expand all sub-nodes.
• Repositories - Sort applied repositories on top or in another list. Currently, we can see all the applied only when we click "Show only applied repositories".
• Repositories - Add an option to filter the repositories by type(font, fill, border, image, and so on). Currently, we can filter them only by name.

To be accessible and compliant with our organizations standards, the search bar that can be enabled in the gridview should be accessible by pressing TAB and shift TAB. Right now the only way to select the search by keyboard is pressing Control F, but the up/down arrows and the search settings cog wheel cannot be accessed via the keyboard.

As of right now, the user cannot also select the column headers using the keyboard, which in turn means you cannot sort by a column with a keyboard.