Intersoft Community - Crosslight - Crosslight and Xamarin components

Crosslight and Xamarin components

Joke — Thu, 18 Dec 2014 09:46:57 GMT

Hi Yudi,

Thanks for answering.It's work well.Thank you!

Crosslight and Xamarin components

yudi — Mon, 15 Dec 2014 08:41:26 GMT

Please kindly check my post on July 8, 2014 7:16 AM. I uploaded the sample in OneDrive. Simply click the link in my previous post and let me know whether it helps or not.

Crosslight and Xamarin components

Joke — Fri, 12 Dec 2014 07:40:08 GMT

Hello Yudi:

Can you send me a Scan QR code code.I'm a student , I want to learn ahout it.My e-mail address is :13372662475@163.com.

Thank You !

Best regards,

Joke.

Crosslight and Xamarin components

yudi — Thu, 10 Jul 2014 23:30:53 GMT

The scenario, to navigate directly from the “Scan” item in the drawer to the barcode scanner without the scan button, is implemented using Executing Commands in NavigationItem technique.

However, in certain scenarios, you might want to execute commands directly in NavigationItem Class. For example, introducing a Logout button that triggers the logout command in the view model.

This technique is documented in Implementing Drawer Navigation section. For more detail information, please kindly check them in http://developer.intersoftpt.com/display/crosslight/Implementing+Drawer+Navigation.

Crosslight and Xamarin components

thomas.albert@tea-net.ch — Tue, 08 Jul 2014 14:15:49 GMT

Perfect. Thanks a lot.

I wonder if I find any documentation about that approach. It would be very interesting to know what is going on under the hood.

Crosslight and Xamarin components

yudi — Tue, 08 Jul 2014 07:16:35 GMT

Is it possible to navigate directly from the "Scan" item in the drawer to the barcode scanner without the scan button?

Yes, you can. Please download and evaluate the sample and let us know whether it helps or not.

Crosslight and Xamarin components

thomas.albert@tea-net.ch — Mon, 07 Jul 2014 11:44:26 GMT

Hello Yudi,

Thanks for the assembly. I just tried it with my scenario and it worked. Great.

I really hope this will soon be stable and included within the next monthly update.

One more thing. My current scenario is: Having a drawer navigation with a list item "Scan". Clicking on the "Scan" item navigating to a new fragment. There having a scan button which opens the scanner. This works fine. Is it possible to navigate directly from the "Scan" item in the drawer to the barcode scanner without the scan button?

Crosslight and Xamarin components

yudi — Sun, 06 Jul 2014 22:55:49 GMT

Apologize for any inconvenience this problem may have caused you.

I enclosed the signed version of Xamarin.Android.Support.v4.dll assembly as attachment. Please have the attached assembly evaluated on your end and let us hear whether it helps or not.

As soon as this nightly build is stable, the project wizard will also get updated so that the project uses Xamarin.Android.Support.v4 assembly.

FYI, the attached assembly has been tested on a simple project which uses ZXing MobileBarcodeScanner. Should you find any unsupported scenario please feel free to let us know.

Crosslight and Xamarin components

thomas.albert@tea-net.ch — Fri, 04 Jul 2014 03:43:48 GMT

Unfortunately the nightly build is not working. I am not sure how you tested it. In my solution I included the zxing.net.mobile-1.4.5component through Visual Studio. This adds a reference to the Xamarin.Android.Support.v4 assembly. I replaced all Crosslight assemblies with the one's from the nightly build. Rebuilding the solution fails with error: The type 'Android.Support.V4.App.ListFragment' is defined in an assembly that is not referenced. You must add a reference to assembly 'Xamarin.Android.Support.v4, Version=1.0.0.0, Culture=neutral, PublicKeyToken=71f3e3261ac778b5'. Though the Xamarin.Android.Support.v4 assembly is included. After doing some investigation I found the problem. See attached screenshot. You added the Xamarin.Android.Support.v4 assembly with a public key token (signed) to the Intersoft.Crosslight.Android assembly, but the component version of the Xamarin.Android.Support.v4 assembly and the original version from Xamarin have a public key token = null (unsigned). So use an unsigned version (which would be the better solution) or deliver the signed version.

Will there be an update of the project wizard, so that the Xamarin.Android.Support.v4 assembly is added to new projects instead of the Mono.Android.Support.v4 assembly?

Please, correct the existing problem and send me another nightly build.

When do you expect this to be stable? I really need this feature in my app.

Crosslight and Xamarin components

yudi — Wed, 02 Jul 2014 23:20:34 GMT

The new update, Crosslight 2 build 61, doesn't include the fix for the Xamarin.Android.Support.V4 problem.
Once the nightly build is stable, it will be combined with the release version of hotfix.

Crosslight and Xamarin components

thomas.albert@tea-net.ch — Tue, 10 Jun 2014 02:55:50 GMT

Hello Crosslight Team,

is Xamarin.Android.Support.V4 a newer version then Mono.Android.Support.V4?

After doing some Google search I get this impression.

Many new Xamarin components reference the Xamarin.Android.Support.V4 assembly.

Why does Intersoft.Crosslight.Android rely on the "old" Mono.Android.Support.V4?

How can I use any Xamarin component that references Xamarin.Android.Support.V4 in Crosslight?

Will there be a new Crosslight version that references Xamarin.Android.Support.V4?

Best regards,
Thomas