Skip to content
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

Issues when using a draggable object on a card #384

Open
hejhog13 opened this issue Feb 25, 2022 · 1 comment
Open

Issues when using a draggable object on a card #384

hejhog13 opened this issue Feb 25, 2022 · 1 comment

Comments

@hejhog13
Copy link

I am trying to use a component that is draggable on my cards. Obviously, due to both the deck and the component reading swipes and drags there are issues. I am considering one of these three workarounds but can't figure out how to make them work. Could anybody help?

  1. All swipes/drags are registered to the card unless the swipe/drag is done on the draggable object (i.e. the draggable object takes precedence). I'm not sure how possible this would be.
  2. Decreasing the swipe "hit box" on the card. Is there a way to only make the top half of the card swipable so then then draggable object can be in the bottom half?
  3. Turning off all swiping and using a button to go to the next card. I think this is a reasonable option as well, but the card messes with the draggability of the object still. Is there a way to turn off the cards panResponder?

Any help would be very appreciated!

@hejhog13
Copy link
Author

Another thought: is there a way to disable the PanHandler until a certain button is pressed? And then swiping would work again after that?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant