It seems the element somehow considmes the scrolling/touch action and the grid does not scroll unless you hit the gap where the custom element does not reach. A workaround is to enforce overflow: auto to the scrollable element of the grid. A sample is attached below. div.rgDataDiv { overflow: auto !important; }
Add support for custom paging in the RadGrid Virtualization functionality. The idea is to enable the retrieval of part of the data from the source of data instead of retrieving all of the data every time. Without this feature the optimization technique is to cache the data source. Example is available at http://www.telerik.com/support/kb/aspnet-ajax/grid/details/virtualization-and-custom-paging
The Filtering context menu is not positioned properly when there is not enough height. It is positioned depending on the top border of the window, making the filters not accessible. Screencast: https://www.screencast.com/t/4dQEAczF9c2 Steps to reproduce: 1. Open http://demos.telerik.com/aspnet-ajax/grid/examples/functionality/filtering/excel-like-filtering/defaultcs.aspx 2. Resize the browser so the last elements of the Grid are not visible 3. Open the Filtering context menu Result: It is shown with too big negative top margin
If a column does not have width set, it will not populate the Columns collection of the ExportInfrastructure in the BiffExprorting event http://docs.telerik.com/devtools/aspnet-ajax/controls/grid/functionality/exporting/export-formats/excel-biff-export To be able to loop through all columns, you need to have width specified for them. This change has been introduced in Q3 2014 If you cannot do this for the standard grid rendering when defining columns, you can use the Grid.PreRender event to loop all columns and set some width for them: VB Protected Sub RadGrid1_PreRender(ByVal sender As Object, ByVal e As System.EventArgs) Handles RadGrid1.PreRender 'workaround for BiffExporting event Columns collection not being populated if the column does not have width set Dim Grid As RadGrid = DirectCast(sender, RadGrid) If (Grid.IsExporting) Then For index = 0 To Grid.MasterTableView.Columns.Count - 1 Grid.MasterTableView.Columns(index).HeaderStyle.Width = 100 Next End If End Sub C# protected void RadGrid1_PreRender(object sender, System.EventArgs e) { //workaround for BiffExporting event Columns collection not being populated if the column does not have width set RadGrid Grid = (RadGrid)sender; if ((Grid.IsExporting)) { for (index = 0; index <= Grid.MasterTableView.Columns.Count - 1; index++) { Grid.MasterTableView.Columns(index).HeaderStyle.Width = 100; } } }
Simply add a Column to RadGrid in the GridColumn Collection Editor of the Configuration wizard. You will note that a value for FilterControlAltText is autopopulated. When you hit Ok, that value is written in the column definition, in markup. If you clear that text in the editor, then, in markup you will find the value FilterControlAltText ="". This is useless clutter, which you should manually remove from the markup. The editor/designer should remove the property entry from markup if you clear the FilterControlAltText from the PropertyGrid in the GridColumn Collection Editor.
Misalignment issue in RadGrid with static headers and simple control's configuration appears in IE.
The navigation icons are not readable in mobile Grid in MetroTouch. Video: https://goo.gl/TrzZ0m Steps to reproduce: 1. Open this demo: http://demos.telerik.com/aspnet-ajax/grid/mobile-examples/overview/default.aspx?skin=MetroTouch Result: the Navigation icons are white
Workaround for the NextPrevAndNumeric mode is to set the AssociatedControlID of the label protected void RadGrid1_ItemDataBound(object sender, GridItemEventArgs e) { if (e.Item is GridPagerItem) { GridPagerItem pager = e.Item as GridPagerItem; Label lbl = pager.FindControl("ChangePageSizeLabel") as Label; Panel pnl = lbl.Parent as Panel; RadComboBox combo = pnl.FindControl("PageSizeComboBox") as RadComboBox; lbl.AssociatedControlID = combo.ID; } } <telerik:RadGrid RenderMode="Lightweight" ID="RadGrid1" runat="server" DataSourceID="SqlDataSource1" AllowSorting="True" AllowPaging="True" GridLines="None" Width="100%" OnItemDataBound="RadGrid1_ItemDataBound"> <PagerStyle Mode="NextPrevAndNumeric" Position="TopAndBottom" PageSizeControlType="RadComboBox"></PagerStyle> </telerik:RadGrid> <asp:SqlDataSource ID="SqlDataSource1" ConnectionString="<%$ ConnectionStrings:NorthwindConnectionString %>" ProviderName="System.Data.SqlClient" SelectCommand="SELECT CustomerID, CompanyName, ContactName, ContactTitle, Address, PostalCode FROM Customers" runat="server"></asp:SqlDataSource>
Currently Linq2Sql expressions are supported. But as Entity Framework is "de facto" the standard for data access in .NET, it would be great, if you also support ESQL expressions. This is necessary for example when data binding to entities in OnNeedDataSource event and filter expressions from RadGrid should be used for adapting query. Thanks, Roger
Property to disable the internal control state which is helpful in scenarios where ViewState is turned off. This should resolve any problems when changing columns and datasource dynamically on PageInit, when sorting/filtering/etc is applied during the previous post.
The problem is a limitation in the current implementation. It is due to the fact that when drag and drop are enabled the grid selects the item(mousedown) using the built-in selection logic. Later when click is fired the row is again selected. The selection logic is designed in such way that if you try to select an item which is already selected it will first deselect it and later select it. It is rather complex and handles various scenarios, altering it will result in a breaking change which is not desirable.
Currently RadGrid supports strongly typed binding to a model and the use of OnCalling DataMethods, but requires additional non-documented code to get it to work correctly. See forum post at http://www.telerik.com/forums/model-binding-selectmethod-defined-in-a-business-object#jyvrnG4qhEOdaXv_pBVt8g for the code requirements. Request putting the ItemType and OnCallingDataMethods into the MasterTableView markup and eliminate the need to override the OnInit call. The markup would end up looking like: <MasterTableView DataKeyNames="intOfficeId" ItemType="Models.OfficeModel" OnCallingDataMethods="grdAssignments_CallingDataMethods" SelectMethod="GetOffice" UpdateMethod="UpdateOffice" DeleteMethod="DeleteOffice" > This would also pave the way to strongly bind the detail grid.