Currently, the RadFileDialogs do not support setting filters without specifying the extensions for the files. This is deemed an incorrect filter pattern and an exception is raised.

We can provide support for filtering files that do not have an extension.

Add a property that formats the time items of the clock displayed in the DateTimePicker. Currently, the format is hard-coded to "t" which displays only the time part of the DateTime object. Adding this will allow to show also seconds and other parts of the date-time when it makes sense.

What you have two separate RadDocking controls it should be possible to drag a Pane from the first control into the other one.

Currently, you can drag and drop panes only in their parent RadDocking control. Allow dragging from one RadDocking to another.

Currently, the RadMaskedNumericInput and the RadSlider elements are used for specifying the alpha value of the color work between 0 and 1. Internally, after the alpha value is updated, it is multiplied by 255 and converted to byte.

We could expose an option to work directly with byte values in the range of 0 and 255 for the alpha color.

The current implementation of the Code128 symbology class used with RadBarcode throws an InvalidSymbolException for characters with codes greater than 127.

As you can see from this table, there are many special characters in Code128 that have larger codes:

https://en.wikipedia.org/wiki/Code_128#Bar_code_widths

It would be useful to have these in applications which need to modify a reader device's behavior with barcode control characters in order to communicate properly.

Having a table, for example, with empty cells, executing the TabBackwardsCommand does not move the caret to the previous cell of the row.

Provide a way to change sort comparer when grouping.

Add support for handwritten (graphometric information) signatures in the PdfViewer. 

Currently RadComboBox supports filtering of the data when IsEditable is True. 

Add a mode where a search box is displayed (when IsEditable is False) in the drop down of the control.  The searchbox should filter the items in the dropdown.

Currently, the RadGanttView control displays an indicator in the timeruler area of the control. Allow stretching the time indicator accross the timeline area where the tasks are rendered (under the timeruler).

Many document elements (like Footer, Header, Note, Comments, etc.) have their own RadDocument instance that serves as their body. These child documents are part of the main RadDocument assigned as the Document of RadRichTextBox.

Currently, to access the child RadDocument elements, you should iterate each different element of the main RadDocument and collect its Body property value.

Add a method to easily collect the child RadDocuments, similar to how the EnumerateChildrenOfType<T> method works. Currently the EnumerateChildrenOfType<T> method doesn't work for searching RadDocument, so you can consider extending this already existing API.

Add localization strings that can be used with the RadRichTextBoxRibbonUI control. Also, add the localization resources in the demos.

Implement child dialogs for Style Formatting Properties Dialog. This will allow users to modify Style's properties related to font properties, paragraph properties, tabs, numbering and borders.

Currently, when setting the Culture property of the RadVirtualKeyboard control, the OS keyboard layout will be changed as well.

We can add an option to control this behavior.

Add support for displaying the full length of an appointment when its length is spread across multiple days.

One cannot build the demos source because of the licensing version.

Add a mechanism to change the fill/foreground color of the funnel icon in the column header. The funnel is a FilteringDropDown element and currently the fill of the icon is hardcoded. 

Add an extra property in the FilteringDropDown element to control this color or sync the current setting with the theme palette (e.g. Windows11Palette), so it can be changed using the palette settings.

Add a built-in API that can be invoked from the AzureMapProvider. The API should allow you to search for locations similar to the BingRestMapProvider's search location API.

Add built-in support for elevation, routing and search location services coming from the Azure Maps service. These are the same features as in the BingRestMapProvider, which will be obsolete in 2025.

• Search Location
• Routing
• Truck Routing
• Elevation