hello,
I am trying to implement serverPaging, serverGrouping with webapi and angularjs
I have implemented serverPaging but i am having difficulties while impelementing serverGrouping with paging.
can you please guide some sample project which can i refer.
I thought that maybe I wasn't using the UI correctly, and I did find a notice in the documentation that grouping + virtual scroll is not recommended, however when using virtual scrolling and grouping, it's impossible to scroll to the bottom.
Is there any plans to fix this; or a way to work around it (calling resize or something at a specific time?) where both can be used?
Here is a minimal case to see what I mean. Run the demo and then scroll to the bottom and you will find that as you collapse groups, more content shows up at the bottom that you cannot scroll to.
http://dojo.telerik.com/AXaRi
Thanks for any suggestions
** And yet we know that scrollable:true will use default scrolling and it all works.

01.$("#testi").click(function() {02. var data=DS.data();03. for (var i=0; i<data.length; i++) {04. var row = DS.at(i);05. if(row.fi==row.en) {06. row.set("ok", true);07. } else {08. row.set("ok", false);09. }10. }11.});For my pie chart, I see that I can set startAngle, but I don't see where I can set the direction of the pie pieces. I would like pie pieces to be added counter-clockwise. Currently, they are added clockwise.
FYI, I am also setting a sort on the data, so the largest is always first. Right now the largest is taking the 12-3pm pie piece, the second largest taking 3-5pm, etc. I want them to go 12-9pm, 9-7pm.
Thanks,
--Ed
The crosshairs in line charts and sparklines do not disappear reliably. This behavior is apparent even on the demo page for sparklines. The result is that there is an extra vertical bar that is stuck on the chart. Hovering over the chart again sometimes fixes the issue.
This behavior can be confusing to a user if the crosshair remains stuck at the end of the chart and the color of the lines look similar, it may look like the data drops off at the end.
In kendo.all.d.ts there is an interface for the AutoComplete select event args:
interface AutoCompleteSelectEvent extends AutoCompleteEvent {
item?: JQuery;
}
In my code this will generate a Typescript error about not matching the AutoCompleteOptions interface:
$("#Data_Part_Description").kendoAutoComplete({
select: (e) => { }
}
What is weird is that if I rename item in AutoCompleteSelectEvent to anything other than item it works.
interface AutoCompleteSelectEvent extends AutoCompleteEvent {
i?: JQuery;
}