Hi,
I'm have a remote view which I'll name here "multiplelocalviews.html" with multiple local views...example below:
<div data-role="view" id="LocalView1" data-layout="default" data-reload="false">
Local View 1
</div>
<div data-role="view" id="LocalView2" data-layout="default" data-reload="false">
Local View 2
</div>
<div data-role="view" id="LocalView3" data-layout="default" data-reload="false">
Local View 3
</div>
When I try and navgiate to a particular local view in this remote view from a different page the app seems to navigate to the correct view then change to Local View 1.
I've tried to navigate using both the following methods:
<a href="multiplelocalviews.html#LocalView1" data-role="button" data-ajax="false" style="width: 100%">Local View 1</a>
<a href="multiplelocalviews.html#LocalView2" data-role="button" data-ajax="false" style="width: 100%">Local View 2</a>
<a data-click="localViewThree" data-role="button" data-ajax="false" style="width: 100%">Local View 3</a>
function localViewThree() {
app.navigate("multiplelocalviews.html#LocalView3");
}
But neither seems to work.
Any advice?
Thanks
is there a way to make kendo work with angular ng-view and using angular routing to load remote views and controllers
for example have something like
<body ng-app="App" ng-controller="AppCtrl" kendo-mobile-application >
<div class="styleView {{pageClass}}" ng-view kendo-mobile-view></div>
</div>
and routing be something like this
App.config(['$routeProvider',
function ($routeProvider, $locationProvider) {
$routeProvider.
when('/group/:id', {
templateUrl: 'pages/group/group.html',
controller: 'ctrl_Group'
}).
when('/Welcome', {
templateUrl: 'welcome.html',
}).
if it is not possible is it posible to have scrollview without initializing kendo-mobile-application?
Hello,
In our application, in case the user clicked a certain button, we need to go back two screens. We do this with the following code:
app.navigate("#:back");
setTimeout(function(){
app.navigate("#:back");//to budget edit
}, 0);
}
Testing this code works well on Chrome. It also works well in our tests on iPhone. However in our tests on Android (Nexus 7) it fails and only the first app.navigate("#:back") is executed. Meaning our app fails to bring the user to the correct view. Do you have any idea what might be the cause and how can we handle it?
Thanks,
Ron.