hi...
A Callout Control is in your roadmap for winforms please ?
thx in advance...
regards,
Users should be able to use the scrollbars of the container controls at design-time.
Workaround: manually resize the editor or drag it upwards
Add the ability to add custom items to the RadPropertyGrid items collection.
I have a custom Fluent theme as a package, it would be nice if there was a way to load packages (Embedded Resource or files) with the RadThemeManager.
Rather than typing this: Telerik.WinControls.ThemeResolutionService.LoadPackageResource("GUI.Themes.Fluent_Custom.tssp");
Right now the RadThemeManager only supports XML files. Feeding it a tssp file doesn't work.
For it to show up in design-time I have to assign it all of the unpackaged XML files and then delete the RadThemeManager for the theme to show up, otherwise the load time is like 7 seconds, where as embedded packages load super fast.
The fluent theme has a lot of XML files and this is a huge pain, supporting 1 Embedded Resource tssp package would be nice.
Would also be nice if the RadThemeManager could apply/change a theme globally somewhere in the SmartTag menu or RadThemeManager properties.
Instead of having to type this: ThemeResolutionService.ApplicationThemeName = "Fluent_Custom";
RadControls are slow when using at design time in a form containing a lot of controls, split containers and table layout panels
Please refer to the provided sample gif file. You will notice that when you are dragging within the same RadGridView control, there is a horizontal line indicating the drop position. The image is controlled by the RadGridView.TableElement.RowDragHint property which specifies the horizontal line illustrating the drop position.
This horizontal line is missing when you drop over another target grid control.
http://demos.telerik.com/aspnet-ajax/treelist/examples/overview/defaultcs.aspx
To reproduce: - Add RadLayoutControl to a form. - Change the Language property at design time. - You will receive the following message: There is already a command handler for the menu command '1496a755-94de-11d0-8c3f-00c04fc2aae2 : 103'. Workaround: - Reopen the designer.
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:
In this case, we have an MS standard Form with control position on the form. Each of the controls has the right anchor. Moving the form to a monitor with a higher resolution messed up the size of the controls.