Introduce support for add/remove instances of child/nested objects.

Handle the case when the cell is too small and the value contains a decimal separator. 

For example, see attached images. 

Currently, the only customization that can be performed is using HyperlinkToolTipFormatString property of RadRichTextBox, which sets the format for all hyperlinks in the document of the control. It would be nice if it were possible to be able to set different tooltips. 

Dear Telerik Development Team,

First of all, I want to thank you for your great work on the RadTileView control for WPF. I appreciate the effort and attention to detail that you have invested in this component.
In my projects, RadTileView has brought significant value thanks to its visual appearance, the smooth animation when maximizing or restoring tiles, and the ability to provide distinct content for minimized and maximized states. It truly enhances the user experience, and I find the dynamic layout engaging and modern.

However, I have faced some challenges related to tile reordering and positioning:

• The drag & drop rearrangement mechanism sometimes behaves in unpredictable or unintuitive ways, especially when there are many tiles or when tiles have different sizes.

• There is currently no straightforward way to specify the exact row and column position of each tile when dynamically adding them from code.

• It would be extremely useful to have a way to control or "lock" a tile to a specific grid position, for example by exposing explicit row and column properties for each tile, or by allowing developers to define the exact layout coordinates when adding tiles dynamically. This feature would make it possible to programmatically manage tile placement in complex dashboards, rather than relying only on the automatic layout and drag & drop interactions.

Such functionality would be highly beneficial in many scenarios, especially for enterprise dashboards where the layout must follow strict business requirements and should not be left to chance or automatic algorithms.

Would it be possible to consider this kind of feature for a future release?
If there is a known workaround or recommended approach to achieve precise tile positioning with the current RadTileView, I would greatly appreciate your guidance.

Thank you again for your work and support.
Looking forward to your reply!

Best regards,

Allow to track points that intercept vertical line from mouse position (as now)  or points that intercept horizontal line from mouse position.
So allow to choose TrackDirection = Horizontal/Vertical

Thanks.
marc.

The RadPropertyGrid control has a built-in keyboard navigation logic when the RenderMode is set to Flat, however, it does not provide an option to navigate outside of the control to other UI elements. Disabling the built-in navigation provides this behavior partially, however, it does navigate through each property definition.

We could add an option that will allow us to retain the current functionality, and allow the users to navigate outside of the control. 

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.

Currently, the chat messages are not virtualized meaning that all message visuals will be layout. Add a built-in UI virtualization feature that will allow generating only the messages in the viewport.

Currently, if you have a cell that merges into multiple columns, when you click on the column header, this will select also the adjacent columns where the merged cell extends. Add an option to disable this functionality and select only the cells in the clicked column.

Currently, the BoxPlotSeries supports only vertical rendering (numerical vertical axis and horizontal categorica/date-time). Add support for horizontal orientation for the series. The orientation should change when the chart axes get swapped - numeric as horizontal and categorica/date-time as vertical.

If a RadTileViewItem hosts several controls (e.g. Buttons, RadioButtons) users should be able to change the focused element using arrow keys.

Currently, when exporting/copying cells from a column that is bound to a nested property, the base logic of the GridViewDataColumn is that it has a separate logic for this setup. When exporting/copying, the column will try to retrieve the display value rather than the underlying value.

Currently, the delimiter is hardcoded to ",". Add a setting that allows changing this and also synchronizing it with the current culture of the system.

Provide text formatting options while typing in the chat textbox. The formatted text should be properly visualized as well. 

Currently, the QueryableEntityCoreCollectionView<T> class forces you to have an empty/parameterless constructor for the T type. This allows easier creation of the items at runtime. However, in some situations it makes sense to allow classes with only constructors with parameters. Such scenario is when following the DDD (Domain-Driven Design) pattern where it is strongly adviced to avoid having empty constructor in your entity classes.

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. 

Enable the customers to create and modify .pptx (PowerPoint) files . They need processing as well as showing such documents.

Expose API that allows you to add/remove Annotations/IPointerHandler implementations from the PointerHandlersController.

Currently, the RadRichTextBox supports only the MS Pinyin. We could add support for QQ Pinyin.