It would be very nice to have a "transpose" functionality in RadGridView. There are ways to transpose data instead of GridView, but this way it would be difficult to configure bindings, styles and other parameters. PivotGrid isn't suitable in this scenario because of lack of editing. There is an example of what is needed: https://rotatedwpfdatagrid.codeplex.com/. I was successfully using this example with a standard WPF DataGrid, but I don't know how to accomplish this in RadGridView. There are already a few threads about this feature: http://www.telerik.com/forums/transposing-columns-and-rows http://www.telerik.com/forums/radgridview-can-be-transposed http://www.telerik.com/forums/displaying-grid-data-in-column-row-format http://www.telerik.com/forums/reverse-column-and-row-in-the-grid Thank you!
The problem was initially reproduced by TestStudio users. It can also be reproduced with a codedUI test where the editor is searched by its AutomationID. Error Message: Microsoft.VisualStudio.TestTools.UITest.Extension.UITestControlNotFoundException: The playback failed to find the control with the given search properties. Additional Details: TechnologyName: 'UIA' ControlType: 'Text' AutomationId: 'CellElement_2_1'
These issues should be resolved with lib version 2014.3.1110.
We would like to have the ability to merge cells vertically with same content. Consider to do the same horizontally.
The problem will be fixed with Q3 2014 official version.
Resolved with lib version 2014.2.0825.
Resolved with lib version 2014.2.0825.
Resolved with lib version 2014.2.714.
Resolved with lib version 2014.2.721.
StackOverflowException is thrown when perfoming sorting, filtering or grouping on GridView bound to DynamicObject
The NullReferenceException is observed when the GridView is Grouped and rebound in the CellEditedEnded event handler.
RadGridView is consuming resources when its IsBusy property is set to False in Windows8, Windows8Touch, Office2013 themes.
Wrong selection when data is real time updated
Pasted rows are not correct after coping all rows with SelectionMode Extended. This is caused by the incorrect count of the cells in SelectedCells collection. Resolved with LIB version 2014.1.0428.