Everything is good and I am using the ASP.NET MVC with kendo. I have seen a few issues after upgrading to 2013.2.918
Strangely all views that were loading via ajax have stopped with the 1013.2.918 release. I can select the Kendo. Menu-->Menu Item with a url reference that points to a controller to return a view to load via ajax and the views is lost as soon as it is loaded. It flickers almost.
Strangely all views that were loading via ajax have stopped with the 1013.2.918 release. I can select the Kendo. Menu-->Menu Item with a url reference that points to a controller to return a view to load via ajax and the views is lost as soon as it is loaded. It flickers almost.
4 Answers, 1 is accepted
0
Hello Ross,
Daniel
Telerik
I am not sure what could be causing the described issue with the service pack release. Could you share the code you are using or a runnable sample that reproduces the problem so I can investigate what is going wrong?
Regards,Daniel
Telerik
Join us on our journey to create the world's most complete HTML 5 UI Framework - download Kendo UI now!
0
Ross B.
Top achievements
Rank 1
answered on 21 Oct 2013, 01:34 PM
Hi and thanks for the reply. I have narrowed the cause down to something that changed in the kendoui effects. We have been using Fade-out and Fade-in to control view transitions the views can contain one or many views that can load child views. The fade-in and out is firing differently in the 2013.2.919 release.
0
Ross B.
Top achievements
Rank 1
answered on 21 Oct 2013, 02:11 PM
The code below seems to fire in reverse if I use currentView.hide() and newView.show() it works but leaves the transitions very choppy.
fadeOutView:
function
(currentView,newView)
{
var
that =
this
;
newView.hide();
if
(that.options.animate) {
if
(currentView.attr(
'id'
) == newView.attr(
'id'
)) {
var
effect = kendo.fx(newView).fadeIn().duration(1400);
effect.play();
newView.fadeIn(400);
}
else
{
var
effect = kendo.fx(currentView).fadeOut().duration(700);
effect.play().then(
function
() {
newView.show();
});
}
}
else
{
if
(currentView.length > 0)
currentView.hide();
newView.show();
}
},
0
Ross B.
Top achievements
Rank 1
answered on 21 Oct 2013, 06:15 PM
I found a possible solution I thought I would share. The actual div being activated to replace the dive being faded out now has an opacity of 0. I guess this is because it was faded out using fadeout but I was calling div.show(). I changed it to use the fadeIn and it works. Working change below.
var
effect = kendo.fx(currentView).fadeOut().duration(700);
effect.play().then(
function
() {
//newView.show(); <-- does not work anymore because opacity is 0 after a fadeout
var
effect2 = kendo.fx(newView).fadeIn().duration(700).play();
}