Unplanned
Last Updated: 02 Sep 2020 11:09 by ADMIN
Hi Team,

I would like to request the ability to reassign the context of a function in the Kendo UI Grid events.  For example, using the DataBound event, setting This to not be the Grid (e.sender) This would be useful to be able to use my TypeScript class methods.

Thank you.
Unplanned
Last Updated: 20 Jul 2020 13:38 by ADMIN

Aligning numeric values in grids is common place and best practise.  Kendo Grid does not provide any neat functionality for this, especially in MVC where the model is strongly typed. Where a MVC grid is bound to a model, the Razor Wrapper would work better if it right aligned columns if for example type int (or other numeric types which are better to be right aligned). Where this needs not to be the case a data annotation would suit.

eg.

public class MyModel
{
   [AlignRight(false)]
   public int ProductID {get; set;}

   public int Age {get; set; } // aligned right by default in Kendo Grid because of int type
}

In the above case ProductID would be left aligned, and Age would be right (which could be the default for all integer types)

With this functionality the razor implementation could also provide an align property to override align functionality.  An AutoAlign property could provide this functionalityto auto detect from model  or not (and also allow this functionality as being off to provide backwards compatibility)

@(Html.Kendo().Grid<MyModel>() .Name("grid")
.AutoAlign(false) .Columns(columns => { columns.Bound(c => c.ProductID).AlignRight(false) columns.Bound(c => c.Age).AlignRight(True) })


Unplanned
Last Updated: 21 Jan 2020 08:12 by ADMIN

add a grid to a view

open the view with data bound to the grid.

First line of data is not selected.

 

Now i have to program the ondatabound property for a function which belongs to the grid component. Make it configurable for grids which do not need this feature or vice versa.

Unplanned
Last Updated: 16 Jul 2019 14:48 by ADMIN
Created by: Tech
Comments: 1
Category: Grid
Type: Feature Request
0
At the moment, it requires converting NodaTime objects into System.DateTime ones in order to be correctly handled by the control. This is suboptimal from both performance and maintainability perspectives.