Issue on Android with latest version of Forms 2.2.0.31 about xamarin-forms-carouselview

[mannyvw]

OK Fixed it. Name of property has changed to an _hScrollView. Easy when you know how!

    _scrollView = (HorizontalScrollView)typeof(ScrollViewRenderer)
                .GetField ("_hScrollView", BindingFlags.NonPublic | BindingFlags.Instance)
                .GetValue (this);

[QianPro]

same problem.

[mannyvw]

Anyone find a solution to this ? Have been trying all sorts of work arounds but nothing working :-(

[Liam-Tait]

Also having this issue

[QianPro]

Yes, it works now! Thanks @mannyvm!

[JRolandros]

Thanks it works perfectly. Good work @mannyvw

[RimVo]

Works like a charm. Thank @mannyvw

[ppongsakorn]

It work!
Thank you.

[repper]

Many many thanks, it worked like a charm... :)

[twentytwokhz]

I am still having trouble with the CarouselLayoutRenderer.cs
At line 40 with latest code from git and latest Xamarin version the _scrollView is still null.
What can I do?

[darylw]

It's worth pointing out here that if you are on a version of Xamarin forms lower than 2.2.0.31, then the reverse of this applies. I.e. the original post by @mannyvw which contains the field "hScrollView" is the correct line, rather than "_hScrollView". The reason I point this out is that the code has been updated to include the newer field, so this code on older versions of forms will break.

Perhaps it might be ideal to check for the existence of the original, and then use the newer one, so that it works with both? Just a thought.

Either way, great post @mannyvw - this saved me a lot of time.

[mannyvw]

Thanks . As an update in a new project I started I also needed a carousel view and there is actually an official from Xamarin now, it was supposed to be included in Xamarin Forms 2.3.0, but it was removed because of stability issues ? anyway it has its own NuGet instead. have been using it on android and ios for past few months and its been fine.

https://xamarinhelp.com/carousel-view-xamarin-forms/

NuGet is Xamarin.Forms.CarouselView

thanks

[darylw]

Cheers for that - I had been keeping an eye on that, but the one thing that was crucial to this for me for UX reasons was the page indicators. This solution contains it from the start, and they are customisable as well, so was absolutely ideal. When Xamarin implement the indicators as well, then I may well switch over to theirs. Thanks for the prompt feedback - appreciated.

[mannyvw]

Yeah my original UX had the pips too , i just did them programatically in forms, although they have been removed now. bloody designers ;-)