iSeller POS Retail
iSeller POS F&B
iSeller POS Express
Latest Development Blogs
Browse By Tag
How do you properly use modal navigation on Android without closing the navigation context once a child view has been closed? We have been using StaysModal property for quite some time with iOS to prevent the NavigationService from closing the modal view context. However, this is not the case for Android when the [x] or save icon has been clicked from a form view.
To be more detailed, here's the scenario. Once app loads, an advanced master/detail view is displayed. The initial sequence goes this way (List A.1 » List A.2 » Detail A.1), before the modal context view is loaded. Once on Detail A.1, a user can click a button to load a modal context (nested modal?) in (List B.1 » Detail B.1) sequence. The Detail B.1 was referred to as "child view" in the first paragraph. Closing Detail B.1 should only close itself, and should not include List B.1, which is working as expected on iOS with the help of StaysModal property as seen on the attached screenshot. On Android... well, it doesn't work for us. Please review and confirm this scenario.
Hi Jimmy,We released this as hotfix which you can obtain it here http://git.intersoftpt.com/projects/CROS/repos/updates/browse/Crosslight4_0_5000_290. Hope that'll helps.
Hi Jimmyso what i understand you want after i press Done in figure 2, i will go back to figure 1 conditon?you can see the figure 1 & 2 in the attachmentIs this right?
Hi Jimmy,Looks like StaysModal is not yet supported in Android, i already inform this feature to our developer under CROS-855, and by the looks of it, will be solved in v4, so stay tune!
Hi Jimmy,Did you mean how can we implement the stays modals? We actually have a workaround, normally iOS doesn't have the stays modal but our engineer find a way to implement it. Anyway Android version staysmodal already implemented and working (i already tested it :)) Please notes it is for v4, and still need further testing for any breaking changes. (we want to make sure when you change version it doesn't break your project)Can you explain me what do you means by breaking the logic of cross-platform implementation? If you are curious i can ask your questions to our dev! :)Cheers,Arief
We actually have a workaround, normally iOS doesn't have the stays modal but our engineer find a way to implement it.
This is already working on iOS with the current version of Crosslight.
Anyway Android version staysmodal already implemented and working (i already tested it :))
Already implemented on which version? When can we expect this to be available?
Can you explain me what do you means by breaking the logic of cross-platform implementation?
Because StaysModal is not implemented on Android, a viewmodel that is expected to run an Action<NavigationResult> resultCallBack delegate is not functioning on Navigate method of the NavigationService. Any logic within that action is not running because the navigation context created with a modal mode somehow bypasses this action. We've implemented some logic for a functionality that is dependent on this property, which is working on iOS.
v4, around this month, we can't give hotfix now because staysmodal may affect other navigation components Also it was along with imminent release of VS2015 and Microsoft Edge (it actually affect our samples and Web Components too based from our testing). But the most important we have a new code generator which we must check extensively or it can break samples and our project templates.
I see, we are very sorry that it should be availlabe in both iOS and Android.
Forgot your password | Sign up
Choose this if you're already a member of Intersoft Community Forum. You can link your OpenID account to your existing Intersoft Social ID.
Choose this if you don't have an Intersoft account yet. Your authenticated OpenID will be automatically linked to your new Intersoft account.
Enter your Wordpress Blogname
Already a member? Sign in