-
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
Detect strenght of throw / Create a "wheel" effect #275
Comments
Hey @QQizi, There is only one callback in the
|
@QQizi By the way, I'm interested in seeing how your "wheel of fortune" looks like ;-) |
@bd-arc Thx for your help. |
@QQizi Unfortunately, the link to your gif doesn't seem to work... Would you mind sharing your implementation with the By the way, your "wheel" idea has motivated me to check if the following kind of design could be implemented with the carousel: And the answer is yes, with nothing but a few lines of code. I thought I'd share in case someone is interested:
|
My wheel looks kind of like yours, kudos 👍 ! Your exemple is dope tho ! The panResponder :
Last question, is there a way to disable the use of the Carousel ? Want the user to not be able to throw again after there throw. Thx for your help ! |
@QQizi Absolutely! The carousel inherits miscellaneous props from Your wheel looks great; I'd love to see how the custom interpolation I've shared would suit it ;-) |
Thx for your help @bd-arc ! I'v tried real quick the interpolation but the "scrollInterpolator" & "slideInterpolatedStyle" did not seem to be triggered. The effect on round slide wouldn't be that obvious anyway. |
The "custom interpolation" feature was implemented in version |
Hi everyone,
I'm currently working on an app with a "wheel of fortune" feature.
I'm using react-native-snap-carousel as a horizontal wheel and it's working great.
My question is, is it possible to detect the "power/strenght" of a throw from the user ?
I don't want the user to be able to select there item by throwing the carousel very slowly.
The text was updated successfully, but these errors were encountered: