Telerik assemblies needs to be rebuild with a specific key in some redistribution scenarios, so that the assemblies can be bound only to a single WPF application. This is described in the following article: https://docs.telerik.com/devtools/wpf/licensing/protecting-telerik-assembly
Currently, to protect the dlls you need to rebuild the entire source code of Telerik UI for WPF. Sometimes this is not very convenient and it is prompt to errors because several steps should be followed and also few prerequisites should be met.
Consider providing a new mechanism to protect the Telerik assemblies, which is more convenient and gives better protection.
Returns a Range object that represents the current region. The current region is a range bounded by any combination of blank rows and blank columns. If we want to be consistent with MS Excel we should implement this property. It is useful for many operations of a region such as filtering(selecting one cell and executing the Filter command should apply it to the current region), sorting, selecting all and etc. This document will be useful: https://docs.microsoft.com/en-us/office/vba/api/excel.range.currentregion.
This action is usually linked to a Button field and with it, the user of the application may revert all field values to their defaults.
FileDialogs are constructed by RadWindow and ExplorerControl as its content. Explorer control holds navigation tree, autocomplete, filtering combobox, main pane for viewing fodler and files, search box, breadcrumb. You can check all visual parts in the following help article: http://docs.telerik.com/devtools/wpf/controls/radfiledialogs/visual-structure Users might need to put the ExplorerControl in non-window parts of their application (for example in docked RadPane of RadDocking. Also, they might need to override OK/Cancel commands for that purpose.
Add an event that indicates when a hyperlink is clicked.
Please add an option to modify the corner radius for TrackBackground and UncheckedTrackBackground in the RadToggleSwitchButton template.
The radius of both rectangles is hard-coded to 9 (TrackBackground) / 12 (UncheckedTrackbackground) (Why are they different btw?). While it is possible to set the TrackHeight and TrackWidth to custom values, this doesn't really work well for the Fluent theme right now due to the radii quickly becoming disproportionally large or small compared to the TrackHeight. This results in the control losing its shape and becoming more and more egg-shaped or rectangular, depending on whether you decrease or increase the TrackHeight.
Ideally, the Radii would be automatically computed, depending on the selected TrackHeight (Floor(TrackHeight/2) ?), however, a manual solution would also be a lot better than nothing. That way we could at lease define proportionally matching values via styles.