Hi,

Is it possible to display two weeks at the same time and slide by one week. For eg, 1-14 -> 8-21. The same would apply for month.

The issue is that when you have an event on the last day of the display period, you can't move or extend it to the next "page".

I have a sortable tab strip that has an editor inside each tab.  It works great until the user starts moving tabs, then all the content that's inside of the editor disappears.  The tab container seems to move properly, it's just losing the actual content within the editor itself.

Here's a link to a demo of the problem:  https://dojo.telerik.com/oDUrupUp

Hello,

is there a way to have shape fills that are more complex than rgb-values, for example a diagonal hatch fill?

my knowledge on the map control and svgis limited. my current approach is to create a pattern via jquery when the map is created:

        jQuery("map svg defs").html(''
            + '<pattern id="diagonalHatch" width="10" height="10" patternTransform="rotate(45 0 0)" patternUnits="userSpaceOnUse">'
            + '  <line x1="0" y1="0" x2="0" y2="10" style="stroke:red; stroke-opacity:0.4; stroke-width:8" />'
            + '</pattern>';

then i use the def as fill for shapes when they are created:

    shape.fill("url(#diagonalHatch)");

this works fine, but i want to have opacity or color depend on other parameters, which would result in many defs.

Do you have any suggestions?

I have a radial guage with 2 pointers.   The initial value can be set in the view model for both pointers but when I change the value in the model using Set, only one of the pointers gets changed.  How can i modify both pointer values?

I've created a dojo showing this.

https://dojo.telerik.com/AkEKaSes

Hi Team, 

To expand on my title, the default value of the 'selectable' attribute is false. However, by accident I discovered, that even if it is false, if you run the select() function on the grid, its default behavior is "multiple,row".

Is this the expected result in this scenario? Personally I would expect there to be no change as i have not specified a selection strategy?

See example, and comment out the selectable attribute: https://dojo.telerik.com/iyaFajoB

Regards, 

Grant

Hi all,

I am looking for a way to put multiples commands buttons, for i.e., "Edit", "Delete", "Print" into one split-button dropdown in Kendo Grid.

I've found these buttons here (https://docs.telerik.com/kendo-ui/api/javascript/ui/toolbar/configuration/items.menubuttons) how I wanted but I am not getting the template right for it.

The idea is to have a default clickable button to "Edit" and an dropdown arrow to select "Delete" or "Print".

Thanks in advance.

I've been chasing down an elusive problem for some time now and I've narrowed it to a logic change in the ListViewItemBinder.refresh() method between Kendo UI versions 2015.2.902 and 2015.3.930 (the issue happens on every version since 2015.3.930).  We have a mobile list view that is bound to a data source.  The template for the ListView creates a Touch widget and a tap handler for each list item.  The tap events and event handlers are working just fine, within this tap handler we change several properties on the data items within the DataSource.  The issue is that in v2015.2.902 these property changes cause the ListView to refresh itself and properly reflect those property changes, but in 2015.3.930 the ListView does *not* refresh itself even though the code has not changed on our end.

I finally managed to isolate the issue to a logic change within ListViewItemBinder.refresh() between the two versions, specifically within the first "if" block.  Here's the logic in 2015.2.902:

In 2015.2.902, action === "itemchange" resolves to true and !listView._hasBindingTarget()) resolves to false, so this block is skipped.  The code eventually drops to the following if/else if/else blocks and eventually calls the very last "else" block which actually triggers the kendo code that re-executes the template and replaces the HTML content (comment is mine):

However, in v2015.3.930, the first "if" block I listed earlier was re-written as follows:

As I mentioned in the comments, this logic change causes us to immediately hit the "return" statement and we never drop into the lower if/else if/else block where the template gets re-executed.  My questions then are as follows:

1. What exactly was the purpose of this change?
2. Is the scenario I've laid out actually exposing a bug, or is there something that I'm doing incorrectly that I can resolve within my own code?

I've tried to mock up this scenario in the Dojo but as of yet haven't quite been able to do it, hence the long post.  Thanks for taking a look!

I have a grid with 10000+ items but with the menu filter mode enabled this poses a bit of a lag issue when trying to populate all of the dropdown options for the filter menu.

So I use:

filterable: {mode: "menu, row"}

Is it possible to have the menu filter mode enabled but disable it on a column by column basis? (See attached image for example of what I mean)

As always, thank you for your help.