Intersoft Solutions - Community - Crosslight - How to Use Crosslight to Prevent Closing Modal Navigation on Android

Create New

New Discussion
New Question
New Product Feedback

Post Reply

Jimmy TungolMember

Posted: June 18, 2015 2:55 PM

Hi,

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.

Thanks!

1 attachment

ItemEditorViewModel.png

Quick Reply

Quote

All Replies

Arief HandanyMember

Posted: June 19, 2015 8:32 AM in response to Jimmy Tungol

Hi Jimmy

so 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 attachment

Is this right?

2 attachments

Jimmy TungolMember

Posted: June 19, 2015 3:12 PM in response to Arief Handany

Well, yes I believe that's how it is. But please note that I am referring to both Tablet and Phone, not just on tablets as you provided on the screenshot. Thanks!

Quick Reply

Quote

Arief HandanyMember

Posted: June 22, 2015 7:09 AM in response to Jimmy Tungol

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!

Quick Reply

Quote

Jimmy TungolMember

Posted: July 15, 2015 10:42 PM in response to Arief Handany

What does it take to expedite this feature? I mean this is basically breaking the logic of a cross-platform implementation. Especially if a viewmodel is expecting a NavigationResult object, which is NOT being returned by the navigation context.

Quick Reply

Quote

Arief HandanyMember

Posted: July 16, 2015 2:29 AM in response to Jimmy Tungol

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

Quick Reply

Quote

Jimmy TungolMember

Posted: July 16, 2015 8:13 AM in response to Arief Handany

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.

Quick Reply

Quote

Arief HandanyMember

Posted: July 21, 2015 3:18 AM in response to Jimmy Tungol

Already implemented on which version? When can we expect this to be available?

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.

Quick Reply

Quote

Jimmy TungolMember

Posted: July 29, 2015 6:06 PM in response to Arief Handany

Guys,

When can we expect this to be available? Crosslight v4 has been released, but this functionality is still not working. I'm not sure how we can stress this enough, but this is really important.

Quick Reply

Quote