-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement 'loop' mode #12
Comments
Good implement for swiper function in react native. and i also hope this feature will be ok asap. ^_^ |
Hey @ranjithnori, to be honest, this is pretty complicated. We've played with different approaches so far, but everything we've tried had a flaw. Still, we are not giving up since we really want to implement this feature. If you are aware of any article or code example that might help us, do not hesitate to share it with us ;) |
@bd-arc Sure thing! 👍 |
@bd-arc this repo has implemented Infinite loop with the same scale animation / multiple slider displayed : https://github.com/juangl/react-native-infinite-carousel. EDIT: I worked on the infinite loop. I duplicated the content, add a |
Hi @MathieuSemain, Regarding your test, would you mind sharing a bit more code so I can have a better understanding of what you did? |
Hi,
And the snapToItem method :
|
Hi @MathieuSemain, Thanks for sharing your code. I have to say that I see at least three issues with this approach:
Since we're considering implementing What are you thoughts about all that? |
Hi guys,
Enjoy :) |
please implement it..... |
Hello, |
Hi @6axter82, I've previously been working on it, but I did face some nasty issues and weren't able to dig deeper until... today :-) It's easily the most wanted feature at this time, and I really want to implement it. My hope is to be able to do so before the end of the month (maybe sooner). Stay tuned! |
Ok guys, I've got some great news: I've been working on the "infinite loop" mode and it's coming along nicely. In fact, you can already use the
You can find the description of the relevant props here. Now I need you to provide me with some feedback so I can fine-tune it before the release! This is still 'work in progress' (mostly on Android), but we're almost there ;-)
|
"react-native-snap-carousel": "git://github.com/archriss/react-native-snap-carousel.git#loop" |
when I add loop={true} to my carousel, I am getting this error: Error while updating 'src' of a view managed by: RCTImageView any idea why? |
At last, I've released this feature in version |
@jsappme I really don't know what is going on with your carousel. Can you open a new issue and share some code? |
Hi, I have tested it on the simulator and it looks nice. I have a small jump though, when I scroll fast and reach the last item of 3-by-default-added cards than I don't see any after. One second after a small jump is seen on the simulator screen and further items are added. "react": "16.0.0-alpha.6", Any suggestions?.. |
@6axter82 Make sure to take a look at the description of prop Note that Hope this helps! |
@bd-arc Thanks, I did implement the
I have three Cards and do 10 clones per side in order to catch up on the gaps at the edges (my previous issue described a bit up in this ticket). I get the print outs of the indices, and when I scroll fast than I get negative index, which is wrong as I after want to check on |
As a work around maybe implement a new property for Carousel, which is move to next card at swipe and not further. Which is not a better solution as we want to scroll fast enough as we want and not go to the lets say 30's card one by one. |
I tried to play with Setting it to 3 with carousel of 3 cards does not break the app, as the indices of newly added cards on the left side do not exceed 2,1,0; In case of |
@6axter82 Thanks for the useful feedback! Would you mind creating a new issue with your 4 latest comments? |
Yes, here it is #183 |
If
autoplay
is set totrue
, the carousel jumps from the last slide to the first one whereas it would be better to provide an infinite loop.The text was updated successfully, but these errors were encountered: