When I bind a change event to the grid it will fire each time I click on the row, even if it is the same row. So the selected row is not actually changing, but the event keeps firing anyways. The same thing happens if I programmatically select the row using the select method. I would rather the change event only fire when when the selection has actually changed rather than on every re-selection. Otherwise, you might as well call the event "onSelect" rather than "change". For extra points, it would be cool if the event received a reference to the previous row that was selected.
This has been the most frustrating "feature" of Kendo UI since transitioning from Telerik MVC Controls. Sure, there are workarounds and I can understand that selecting a row changes its state, thus we should use the change event, but with how many other interactions that fire the change event it becomes more or less confusing to work with. If you do a google search for how to attach an onrowselect event to the grid, you'll find hundreds of users posting the same questions time and time again. Often times, each user will end up with a different answer because there isn't a single "onselect" event. This should be a dead giveaway for change.
Agreed! The frustrating point of the change event is that it fires as soon as you click on anything in the row, even command buttons or the detail icon!