I am working with the Kendo mobile framework and am trying to use the bootstrap theme:
<link href="Content/kendo/2017.2.504/kendo.common.min.css" rel="stylesheet" /><link href="Content/kendo/2017.2.504/kendo.default.min.css" rel="stylesheet" /><link href="Content/kendo/2017.2.504/kendo.mobile.all.min.css" rel="stylesheet" />
var app = new kendo.mobile.Application(document.body, { skin: "bootstrap" });
This isn't working, so I'm wondering what the proper css files are.
Hello,
When I change the material theme to the default theme, the image inside the image-only button is not vertically aligned in the middle anymore: http://dojo.telerik.com/enefU/3
I have a similar issue with toolbar buttons too: http://dojo.telerik.com/OCICi
Currently I am trying to solve the issue with following CSS style, but it's not perfect:
.k-button .k-image {
vertical-align: middle;
}
Any recommendations?
Best regards,
Kaan
Is there a way to add a target marker in the donut chart?
There are three slices in the chart. The first slice is the actual value, the second slice is the remaining value to reach the target and the third slice is the remaining value to 100%. See image: kpi-target.png
If the target has been reached or surpassed then the chart will be two slices (actual value and remaining to 100%). See image: kpi-target-2.png
Thanks.
We have 'selectable' set for our scheduler as it adds great easy and fast time selections while the user has the editor open (took out modal overlay to allow them to interact with scheduler while editor is open).
However, this has the unfortunate side effect of browser behavior jumping down the page to focus the scheduler when you click inside if you were not previously focused on the scheduler...
I solved this by setting the height of the scheduler to the users browser window height, so the scheduler is always in view and the jumping stops. My only concern is that the all day slot is not included in the scrollable scheduler section (the overflow of the scheduler time slots that don't fit in the view). Therefore... if someone has 20 all day events they are seeing in the current view, it is going to push the rest of the scheduler halfway down the page and greatly reduce visibility, but we need the all day slots.
Is there a better way to handle the browser jumping issue? Or is there a way to set a max height on the all day slot and make that scrollable? Or have it be part of the scrollable part of the scheduler?
Hello,
I do not see the Show Business hour toggle button or footer in my Scheduler. Even in Kendo demo Basic Scheduler HTML Shows the button but ASP .NET/MVC demo does not. What am i missing. When i am Setting workdaystart and workdayend will it still Show the ShowBusinessHour button?
@(Html.Kendo().Scheduler<MvcDesktop.Models.Scheduler.TaskViewModel>()
.Name("scheduler")
.Date(( DateTime)ViewBag.CurrentDay)
.WorkWeekEnd((int)ViewBag.WorkWeekEnd)
.MinorTickCount(Convert.ToInt32(Session["interval"]))
.WorkDayStart(new DateTime(System.DateTime.Today.Year, System.DateTime.Today.Month,System.DateTime.Today.Day,ViewBag.StartHour, ViewBag.StartMinute, 00))
.WorkDayEnd(new DateTime(System.DateTime.Today.Year, System.DateTime.Today.Month,System.DateTime.Today.Day,ViewBag.EndHour, ViewBag.EndMinute, 00))
.Height(800)
.Views(views =>
{
views.DayView(dayWeekView => dayWeekView.Selected(ViewBag.ShowDay).DateHeaderTemplate("<span class='k-link k-nav-day'>#=kendo.toString(date, 'ddd dd.M.')#</span>")).ShowWorkHours(ViewBag.ShowWorkDay);
views.WorkWeekView(workWeekView => workWeekView.Selected(ViewBag.ShowWorkWeek).DateHeaderTemplate("<span class='k-link k-nav-day'>#=kendo.toString(date, 'ddd dd.M.')#</span>"));
views.WeekView(workWeekView => workWeekView.Selected(ViewBag.ShowWeek).DateHeaderTemplate("<span class='k-link k-nav-day'>#=kendo.toString(date, 'ddd dd.M.')#</span>")).ShowWorkHours(ViewBag.ShowWorkDay);
views.MonthView(workmonthView => workmonthView.Selected(ViewBag.ShowMonth));
})
Thanks
Anmaika
See the live Telerik Demo: http://demos.telerik.com/kendo-ui/spreadsheet/sorting-filtering
Steps to reproduce:
1. Click the filter dropdown on the "Client" column header.
2. Expand the "Filter by value."
3. Check the top 5 client names.
4. Click the "Apply" button.
5. The grid refreshes with the filter applied.
6. Click the filter dropdown on the "Client" column header (again).
7. Click into the filter by condition.
8. Select "Text contains".
9. Type "hill".
10. Click the Apply button.
Notice nothing happens when it should apply the filter and show the item "Agnes Hill".
Problem:
This is broken behavior and doesn't match what Google Sheets or Excel does. Nor does it act in a way that is user friendly. Both Excel and Google sheets allow you to select *both* a filter by value *and* a filter by condition. In the current Spreadsheet implementation, it seems broken and you can't do this unless you apply the filters in the reverse order (first by condition, then by value) - in which case the filter for "condition" in the dropdown loses the filter value (another bug).
Expected behavior:
After step 10, the filter should be applied.
Hi Telerik folk,
Once upon a time, I stumbled upon on an undocumented "feature" - Kendo Grid template take javascript function as value. e.g:
{ // taking function as value template: function(data) { return "Name: " + data.name; }, // string template template: "Name: #: name#",}I vaguely remember reading somewhere (in this forum?) there is a performance different between passing a function to template option vs passing string version. Can you confirm that? If so, how (is it memory usage? CPU? rendering time?) and why? We are finding this "template function" to be very convenient and want to use it more, but want to know if and what price we pay for it.
Thanks you.
I create a TabStrip something like this, where "#myStrip" is set up to have a bunch of tabs, all loaded with Ajax. After it is initialized, I immediately call select() to set the default tab
var widget = $('#myStrip').kendoTabStrip({ // contentUrls set up here, etc.}).data('kendoTabStrip'); // widget.activateTab(3); // doesn't help?
var retval = widget.select(3); // async?var selected = widget.select();
With the Ajax loading, I think the sequence is:
My problem is that during (3), a script on the ajax-loaded content wants to check what tab is selected. It does something like $('#myStrip').data('kendoTabStrip').select(), but the select() getter doesn't actually return anything (0-length jquery object). My guess is that the initial select(...) setter in (2) hasn't actually finalized setting whatever internal variable it stores the current tab info in. It only does that sometime between (4) and (5), and for anything that calls select() before that, like my ajax content initializing at (4), the widget doesn't return what will be the tab element shortly.
I tried using "activateTab()" instead to avoid triggering the "select" event, but select() still doesn't seem to return anything until after the contentLoad/activate events have fired. I could probably have the ajax-content stash a function that does what I want, and have a contentLoad handler call that function so that select() would be valid by that point, but I'd like to avoid that if possible. Do I have to assume that it is not legit to do select() during the content loading process, before it has finished and fired "contentLoad"?
I tried to modify the ajax demo as an example, but there wasn't an easy way to provide my own custom ajax tab content with a script that called select().

Hi,
few days ago DatePicker and CurrencyTextBox stopped working in Chrome when version 56. has been realesed.
Date picker and currency text box are not binded any more, there is no value displayed.
I checked out the console messages and I found there following 2 messages
The specified value "2.1.2017." does not conform to the required format, "yyyy-MM-dd".
The specified value "10000,00" is not a valid number. The value must match to the following regular expression: -?(\d+|\d+\.\d+|\.\d+)([eE][-+]?\d+)?
Everything works fine in other browsers Chrome ver. 55, Firefox or IE, without these console message.
Version of Kendo is 2013.3.1324.
Can you explain why this happened in new versions of Chrome and how can we easily fix this serious issue?
Thanks,
Aljosa