-
Notifications
You must be signed in to change notification settings - Fork 61
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
[Custom] SwipeEvent #10
Comments
With current version I think there is no way And since I don't know your exact needs and situation I will try to make some guesses
Also is this an issue on both platforms or specific to Android/iOS? |
The last option is the better, tbf, or, expose the event, so I could have my SwipedUp implementation. This is for Android and iOS. Thanks! |
I added both, although I will test the iOS version tomorrow Available properties will be: DisableSwipeDetection="True"
SwipeUpActionEnabled="False"
SwipeUpCommand="{Binding SwipeUpCommand}" I will run the build/nuget push now, you might be able to test iOS before me |
1.0.3.44 will contain the new functionalities |
It is almost perfect, thank you so much for the support.
In this method, you should override the SwipeUpCommand, and not invoke the ToggleCalendarSectionVisibility, if there was a SwipeUpCommand defined. At this moment, I have detected my swipe, however, it is still hiding the calendar, which I don't want (at least not your default method) |
I made it so that you can set: SwipeUpActionEnabled="false" This way you will override it Sorry if it wasn't clear |
Oh, you are right. Well, I've managed to do what I needed. Thank you so much! |
Maybe I will rename it to I will add a feature request issue for remaining todos for other direction swipe overrides |
Yes, that would make it more clear. Indeed having all actions bindable would be great. Would serve all purposes for anyone. thanks again. |
How can I deactivate the SwipeUp gesture from this calendar? I want to override it / disable, to call my own SwipeGesture in my view, is it possible?
The text was updated successfully, but these errors were encountered: