I have the following problem:
I have a kendoUI grid and I execute the following steps:

1. I add a row to the grid.

2. I click "Edit"

3. I click "Cancel"

The row disappears.

<script>
$("#grid").kendoGrid({
  columns: [
    { field: "name" },
    { command: ["destroy", "edit"]}
  ],
  dataSource: {

    schema: {
      model: { id: "id" },
      fields: {
              id: {type: "number"},
            name:  { type: "string", editable : true},
               }
    }, 
  },
  editable: {
    mode: "inline"
  }, 
   toolbar:[ "create"],
});
</script>

Hello, I have a requirement to change categoryAxis labels positions as per the negative and positive value so that they don't overlap with the bars. Like the one in below image. I tried the label rotation property, but it gets applied to all the bars irrespective of it's value. Is there any workaround to achieve this?

Hi, 

When I'm customizing the kendo tooltip with a custom class, setting the custom class to be added in the show event, the position of the toolbar is not correctly loaded when I'm setting a padding in this class. This happens only the first time showing the toolbar.

Is this an known bug that I should know about? Is there a fix or workaround for this?

I'm using kendo-ui": "^2019.1.2"

The latest update contained two changes to the filter row that are undesirable. 

The first, the filter row control now has an X in it. On smaller columns, it eats up a lot of the real estate. It is also redundant because next to the filter row operator, is a reserved spot for a clear button. Is there anyway to either remove the clear button from the text editor or remove the clear button next to the filter operator?

The second issue is the noDataTemplate. In my case, I don't want auto complete on the filter row text box. To remove it, I set the dataSource to an empty object. Unfortunately, this results in the textbox to constantly show No Data Found as you type. Is there any way to remove this feature for the filter row controls when the datasource is set to { } for the field?

Thanks.

Drag-and-drop reordering between sibling nodes in the TreeList widget is a feature I've been greatly anticipating, and I'm happy to see it available in the 2020 R3 release. Unfortunately, in its first incarnation, it has some serious reliability issues and doesn't seem production-ready to me. See the attached screen recording of the widget's demo page and observe the steps I take:

1. I drag Rinah's node to the upper border of its current position, which is also the bottom border of Akeem's node. Nothing happens, as expected.
2. I do the same thing again, but this time, it reorders Rinah before Akeem.
3. I then drag Rinah to the upper border of its current position again, which is also the bottom border of its parent node Hyacinth. Instead of the expected behavior of nothing happening, Rinah becomes a sibling of Hyacinth ordered after her.
4. I drag Rinah back to be a child of Hyacinth again so I can retest the same action from step 3.
5. I repeat step 3. Rinah becomes a sibling of Hyacinth again, but this time she is ordered before Hyacinth instead of after her.

From these steps, I can identify two bugs and a UX suggestion.

• Bug: Steps 1 and 2 should not have produced different results. The same action should consistently produce the same result.
• Bug: Dragging a node to the upper or lower border of its current position should not trigger any reordering action.
• Suggestion: Implement you drag-and-drop reordering UX to be more like DevExpress's TreeList. In their implementation, dragging a node to the upper or lower border of its current position does not even show a reordering indicator, making it obvious to the user that they're not going to reorder anything. In addition, their styling for doing a sibling-level reordering (a thick horizontal line across the entire length of the row where it's being reordered to) versus a re-parenting (making all four borders of the new parent appear thick while you're hovering over it) is much more intuitive in my opinion. It's very obvious when the node is going to be reordered, re-parented, or neither. See the other attachment for an example of what I mean.

In my project i have a requiremenr to customize the today button label in the scheduler. And the new lable can have more than one value, based on our requirement. As far i have investigated i couldn't find a proper solution for this. 

currenlty to customize view names(ex: week, month, timeline,) i am changing them in the configuartion like below,

views = { title: ''MyMonthLable', name: 'month',  type: 'month'}

i would like to know whether it possible to do the same for the Today button lable in each view in the configuration, (or any available template to do so)

If this is not possible i would like to which method in your source code returns the lable for Today button, so that i can overrride in each view class and cutomize it to return the new lable. (currenlty i am using this similar pattern and overrride dateForTitle(), and some other methods)

Thank you.