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
Thanks all for your continuous support! We hope you're enjoying a great app development experience with Crosslight.
As we're using our own products to build cross-platform apps for our enterprise clients, this allows us to add a vast array of business-oriented features to Crosslight in a relatively fast iteration. We hope you find the upcoming new features exciting and useful.
We'd also love to hear feedback from the Crosslight community. If you have any features in mind that you would like to see, please file a feature request here.
Stay tuned for our upcoming announcement!
Cheers,
Dear Nicholas,
Please make sure you inherit your custom table source from ObservableTableSource as in the data sample. That's because the table source provided by Crosslight already include the required implementation that comply tothe ViewModel pattern.
If you still experience issues, please send over a sample and we're happy to assist you solving the issues.
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!
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.
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.
Dear Domingo,
Thanks for your patience. Build 51 is now available in our nightly build server which addressed this issue. Please give it a spin and let us know how it works in your end.
For complete details, see Update 1 Release Notes.
Hope it helps!
We've improved the License Manager to address the missing product issue when upgrading to a new release. Could you please try the License Manager and see if it works fine in your end?
Note that one of the registry entries should contain Crosslight 2, i.e., whether it's in the 64 bit registry or in 32 bit. If you cannot find it in both registry entries, you might have deleted incorrect entry previously.
Dear Eric,
We're pleased to announce that 2013 R1 Service Pack 1 is now available for download. The update includes full IE 11 support for all ASP.NET components and Visual Studio 2013 ready across all platforms. You can download the latest installer by signing in to your account at intersoftpt.com/account, then click on the Licenses tab.
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