1. Select the first row. 2. Hit Ctrl-End to jump to the end of the list. 3. Hold down the Shift key and select the last row. 4. Scroll up and notice that everything between the first page and the last page is not selected. * there is a sample project attached in the support thread
The performance of the RadGridView scrolling diminishes significantly when the grid has thousands of rows and alternating row styles are used. This causes scrolling to be virtually unusable. I note this is a known limitation of the RadGridView from information from https://docs.telerik.com/devtools/wpf/controls/radgridview/troubleshooting/performance We have had to remove the alternating row styles from our current product while porting to the RadGridView. I am requesting if this issue is going to be fixed in the future anytime soon.
I am setting the status of the item to Declined as the reported behavior is due to the fact that the RowDetailsVisibilityMode is set to VisibleWhenSelected. The default behavior of RadGridView is to split the merged cell when a row with expanded row details is added. Thus, the reported issue you are is the expected one. If setting the RowDetailsVisibilityMode is removed the control will behave as expected.
The reason for declining the item is that a possible fix for this behavior would practically interfere with the virtualization mechanism of the control. Shortly said, when the columns have their width initially set, RadGridView is aware of the column with the biggest size and performs its calculations based on it. When their size is changed on loading, the control cannot be aware of the size of a column that is not present in the viewport thus, the reported issue is observed. In order this behavior to be modified so, the engine needs to measure an element that is not yet loaded. We cannot commit ourselves to implementing this, as this would affect the virtualization of RadGridView. A possible workaround would be to avoid setting the Width of the columns initially in XAML.
When RadGridView is bound to a ListCollectionView and the SortDescriptions are set, columns with a SortMemberPath different from the DataMemberBinding don't display the sort indicator in the column header. In the attached example the "Status" and "ETA" columns are sorted. "Status" header does not display the indicator due to the SortMemberPath being different from the DataMemberBinding.
In an application, I bind a DataTable with many rows to a RadGridView. As soon as, the datatable is binded, I see the memory needed by the application growing. The problem is that the binding is done each time the content of the DataTable is changing. It seems that the memory is never cleared and keep growing until a MemoryException is thrown. This does not appear with a WPF standard GridView. Do you know why ?
I have a RadGridView and bind its ItemsSource and its SelectedItem to properties of the ViewModel (DataContext). When the ViewModel is created, the property bound to ItemsSource is filled and the property bound to SelectedItem is set to one of the items in the collection. However, when the GridView is displayed, the property is first set to null and then set to the first item in the collection. I assume that the binding of the SelectedItem is evaluated before the binding of the ItemsSource, so the grid is empty and the desired item can't be selected. Is there any way to influence the order, in which the binding are evaluated? Or is there any other way to avoid that the SelectedItem is changed? A similar issue is described here: http://www.telerik.com/forums/selecteditem-binding-issue Unfortunately, I couldn't to find the support ticket mentioned in this thread.
Edit: We are declining this bug as originally the export options were not meant to respect group properties but only some global GridView properties. However we will add such option in GridViewDocumentExportOptions class. You can follow this feature request => https://feedback.telerik.com/Project/143/Feedback/Details/229211-gridview-add-option-in-gridviewdocumentexportoptions-to-include-exclude-grouph
Add a TextAlignment property to the GridView's AggregateFunctions to set the alignment of the resulting text. Apply to both Caption and FormattedValue simultaneously. This way we won't have to make custom ItemTemplates for the AggregateResultsList in each footer, when using AggregateFunctions out-of-the-box.
Can you add a grid-level option to hide any grouped columns automatically (rather than at the column level)? I've tried creating a attached property behavior to do this (see attached), but it doesn't work well with auto-generated columns.
Would you please confirm the following bug? When selecting multiple rows of a *child* RadGridView, with multiple rows having optional nested RadGridViews, scrolling off the content of the WPF app causes the selection of those child grid rows to become unselected after scrolling back to the main selection of the child grid. If you must require a demo in order to get this feature fixed I might be able to extract one based our production application, but basically we have a Telerik grid control with nested grids that we want to maintain child selections on. Thank you, John Wilkins
Right now, if you programmatically increase the RadGridView's font size, the columns get bigger to accommodate. So far, so good. But if you then make the font size smaller, the columns stay the same large-font width. Further, double-clicking the gridsplitter that separates the columns after the above procedure doesn't resize the column like it would if you'd manually resized the column and then double-clicking the gridsplitter - instead, nothing happens. Finally, it would be nice to have a programmatic interface to autosize the columns, something like MyGrid.Columns(0).AutoSize() Thanks!
I have a custom column based on GridViewBoundColumnBase. In it I override GetCellContent. If I bind the column to a nested property (MyProperty.SubProperty), what I return in GetCellContent is not shown, instead the nested property's "raw" value is shown. Attached is a project illustrating the issue.
The grips on the scrollbar's thumb is blurred on 120dpi as well as some of the borders. As it turns out, we hit a WPF specific problem with 120 DPI. The issue is similar to the following: http://connect.microsoft.com/VisualStudio/feedback/details/798513/wpf-dpi-rendering-issues-with-two-borders For the time being this issue is not addressed and most probably would not be fixed.