Based on the examples here (http://demos.telerik.com/kendo-ui/web/grid/editing-custom.html), "incell" editing allows editing a single cell at a time. The edit mode is activated upon a single click in the cell. I would like to have a way to combine this with "cell" selectable mode, e.g. like this? * A single click on a cell selects the cell and fires the "change" event. * A double click on a cell activates the edit mode for the cell.
Hi, Please refer to the following forum for more detail about the problem and my suggestion: http://www.telerik.com/forums/grid-row-navigation-by-keyboard#ncKqVMBBqUe5ZymNXwpFgg Summary: I think in Grid widget, there should be difference between selectable="cell" and selectable="row" (for keyboard Up&Down Arrow navigation). or perhaps you want to add another choice, example selectable: "row cell" (to replace the current setting for "row") and the selectable = "row", just select the row not cell and also DO NOT go to grid header! I believe it's good that you enhance/solve this shortcoming inside the Grid design, because developer like us who has already decided row selection (selectable: "row") during design-time, it doesn't make sense that still the keyboard navigation is at the cell level, isn't it? Thank you.
I have a grid with Column Employee Name and i have Employee names as John and john. As you see the names are same but case sensitive is different. When i group the column Employee Name. The Kendo grid treats it as separate values.
There is an option to freeze the left most column of the Kendo Grid by setting the lockable property. But this is limited to the Left Hand Side columns only and there are no ways suggested to freeze the Right Most columns.
When performing Edit on a real-time grid, hide edit button to prevent simultaneous editing and data overwrite. There was a similar solution previous to signalR integration, http://www.telerik.com/forums/using-kendoui-grid-with-signalr#-3DZMT4HHE-rOWdEf_1mgQ But with SignalR enabled grid, this could all be built-in.
I have a list of entities with a large set of fields, but I don't want to load and display all of them in the grid. Entities have also a couple of complex properties which are displayed via checkbox lists. Though, I want them to appear when editing a single entity. For now, I'm using custom "create" and "edit" pages, but it would be great to have an "url" option for popup editing. This url would return some html (MVC partial view in my case) which would be rendered in the popup window.
The command button set should be configurable on a per row basis. This can be accomplished by accepting a lambda function for the column.command configuration attribute. Presently only a string or array is accepted
Add a property to the grid or the grid row template for setting the max and min height of rows in the grid. If the content on a cell exceeds the available space when the max row height has been reached then show a "More..." button/link in the lower right corner of a cell - if the user clicks this then display the full contents of the cell in an overlay or otherwise show the full contents in a tooltip that shows when you hover over the truncated cell.
The refresh button availability should be indepent from the grid being pageable. The user may want an updatable grid without having page navigator.
When scrolling data in a grid using the virtualization scrolling option, the query to fetch the next section of data will occur twice. It does not happen for every query, but it does happen all the time regardless of scrolling fast or slow.
In lieu or as part of select-all capability: Expose a way to retrieve the filtered set of data (or keys) in the grid and other filterable controls. In other words, when a user has applied their own filters, there is currently no method to retrieve the filtered set across the entire dataset. That makes implementing a select-all button a bit tricky as you have to either select all on the current page (view) or the entire unfiltered dataset and then apply the filter yourself.
Currently Kendo UI grid don't have any way to know that grid changes its mode from edit to view in case of incell editing. As per thread (http://www.telerik.com/forums/is-there-any-way-to-know-grid-edit-mode-changes) we have to add blur/focusout event handler to know changing mode. But some time it happen (in case of adding custom widgets through columns editor) that blur/focusout event triggered but still grid is in edit mode. Its better to have an event when grid changes its mode from edit to view so that we can minimize issue mentioned above.
We use the Kendo Grid with a DataSource connected to an OData service. We also use the OOB Kendo Grid functionality to hide columns in the UI (column.hidden = true). Through testing we found out that the Kendo grid does not use the OData option of selecting specific columns for retrieval. The grid will request all columns for a table, which leads to overhead in the amount of data sent from the server to the client. We sometimes have tables with 50 columns, for which only 10 columns are shown.
"NoRecordsTemplate" - At present a small text is being shown at the bottom of the grid if there are no records which is not prominent. please add back the NoRecordsTemplate so it can be displayed inside the grid and can be customized "Clear all filters" - It is very tough to clear filters one by one please all clear all option
Provide support for momentum scrolling in Mobile Safari for virtualization of remote data grids. http://demos.telerik.com/kendo-ui/web/grid/virtualization-remote-data.html
Please add the option for aggregates to be calculated dynamically by the datasource without requiring the grid to carry out a full refresh. The current workaround from forums is: save: function (e) { // Refresh aggregates when editing e.model.one("change", function () { gridDataSource.fetch(); }); }, but as this triggers a refresh of the databound grid, it's current focussed cell is lost. Example methodology for expected behaviour of solution: 1) A Config Flag on a datasource to recalculate aggregates when a value has been changed (only valid when aggregates are calculated locally) - this stops from requiring the save event. 2) Add support to the grid so that if the aggregates are updated then the grid will only refresh the footer rather than the whole grid. Alternatively the grid could always keep the currently focussed cell between refreshes (assuming the row has not changed, track by model's id field?) Originally queried in forum: http://www.telerik.com/forums/grid-navigation-reset-to-first-cell-after-editing Thanks Euan
Currently its possible to set static attributes or CSS classes to kendo grid columns by specifying then in column definition: var columns = [{ field: 'someData', title: 'Some Data', attributes { 'class': 'some-css'} }]; Please add possibility to add custom attributes or CSS Classes dynamically (depending on data row): var columns = [{ field: 'someData', title: 'Some Data', attributes { 'class': function(dataRow){ return dataRow.data > 1 ? 'css-go-up': 'css-go-down' }} }]; Just similar how it works with template for column. Thanks, Val
Expose a clean way of destroying kendoDraggable. For instance at the moment I only want selected rows in a grid to be draggable, to when a row is selected I make it draggable, but then I need to clear all other draggables in the grid. Can't find a clean way to do this.
With the kendoGrid, if no columns are specified, all columns are automatically rendered. However, dates (at least, I have not tested other non-strings) are rendered in non-human-readable form (at least if they are from SQL Server). Since date rendering is tied to culture parameters, it would make sense to specify culture at the grid object level and have dates, currency, etc. render according to that. It would also be great to have filters setup for these different types applied to dynamic columns.
When we have a Grid with Resizable Columns we may need some of them to be non-resizable (ex. a column containing only status icons). There are work around and customizations: Column Resize - Min Width on Resize http://www.telerik.com/forums/column-resize---min-width-on-resize but I believe it will be more handy to define requested behavior as a property of the specific column (ex. in row template). Also, for non resizable columns the user should not even take a resize handle when going on a non resizable column boundary instead of try to resize and when the user leaves the resize handle the column is bouncing back (restoring) the minimum width defined. Regards, Thomas