iSeller Commerce
iSeller POS Retail
iSeller POS F&B
iSeller POS Express
Crosslight
WebUI
ClientUI
What's New
Download Trial
Web Solution
Mobile Solution
Enterprise Solution
Custom Development
Blog
Community
Latest Development Blogs
ForumPostTopic
Browse By Tag
Hey Guys,
I am not sure if this has been posted or been observed before... but, I have noticed something unusual with MyInventory project since v1. When clicking (+) to add an item, a form view comes up in modal context for users to enter data. However, when you select an item from a Selection editor, the modal context will close. That said, an item cannot be added. This doesn't happen on EDIT mode, maybe because when you edit an item it's in normal context.
Now that we are using the same process to add item, we are having trouble getting it to work since adding requires a modal context. Am not sure if this is bug or adding an item was not implemented properly in MyInventory project. Any ideas? Please advise.
Thanks!
Hello Domingo,
Apparently it's not an issue with the Crosslight product bits. But you'll need to set the StaysModel property of the NavigationResult to true.
In line 55 of CategoryListViewModel.cs, change the code to:
this.NavigationService.Close(new NavigationResult(NavigationResultAction.Done) { StaysModal = true } );
StaysModal instructs the navigation service to keep the modal context if it's currently in modal state.
Please let me know the result in your end.
Hope this helps!
In the attached video, the modal context doesn't close when user select an item from a selection editor. For your information, I'm using MyInventory project with the latest build of Crosslight (build 51) - available in here.
Hi Yuri,
Thanks for showing the video; however, you did not select an item from the categories. See attached video.
Thank you very much for the sent video. I’m afraid that the latest build of Crosslight (build 51) is not successfully applied to the project yet.
Please check MyInventoryModalContext2 video. On this video, I select an item from the Categories.
This should help.
Edited on May 23, 2014 5:45 AMReason: provide link to download video
Sorry for the inconvenience. Please download the video from here.
I don't believe MyInventoryModalContext2 video is attached somewhere.
Thanks for your response.
I’m afraid that the latest build of Crosslight (build 51) is not successfully applied to the project yet.
I'm not sure I undertood this context. Are you saying I downloaded the wrong build? Or this fix was not included on build 51? Or is there something that needs to be done on MyInventory project to fix the issue? I don't follow, please clarify. You mentioned something would help, what would that be exactly? I don't believe I see any video.
FYI: I was using the same version when I recorded that video.
Please advise. Thanks!
It seems Yudi has edited his post which include the video download link now, see above.
Adding to Yudi's reply, the fix is in build 51, that should be correct. However, the assemblies must be properly copied to the correct folder for it to take affect. For samples that downloaded from Git, you'll need to apply the assemblies to the bin folder (Crosslight 2\bin). This presumes that you've followed the sample guidelines here.
Once the assemblies are applied, you also need to clean the solution (all projects to be exact), then rebuild them. This ensures Xamarin Studio picks up the new assemblies and packages them properly.
Okay, it bothered me to see that even after build 52, it wasn't working. Now, after looking at the form's metadata and comparing it to other MyInventory samples, a culprit was identified. This selection category has a customized view controller; however, what triggered the abnormality on its behaviour is the "ReuseExistingViewContext = true" property for the SelectionInput attribute. Removing this property from the attribute made the selection work as expected on default view controller. But, removing the said property prevents the custom UITableViewController to work, as assigned on NavigationTargetIdentifier.
[SelectionInput(SelectionMode.Single, DisplayMemberPath = "Name", ListSourceType = typeof(CategoryListViewModel), ReuseExistingViewContext = true, NavigationTargetIdentifier="CategoryListViewController")]public static string Category;
This sample project was provided Jack on this thread "How to Use EditorType.Selection and NavigationTargetIdentifier to Enable Searching?"
Thanks for pointing out the culprit. It makes sense now as it appears we both are looking at different samples/scenarios.
The selection in custom ViewController case might be still an issue which is separate from the previous one. We are working on a fix shortly. You will be informed when a new nightly build is available.
Awesome! Thanks Guys!
or
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