Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
there is no api (or guidance) on how to add our own gestures.
This is odd, seeing how easy it would be for us to do this. This exasperates the fact we only have one gesture right now (tap).
Can you guys please give us hooks (via base class, or meaningful interface) to be able to add our own gesture recognition?
I've created a mechanism to easily create gestures for xamarin forms. I've implemetned the iOS ones. It's all composition, none of that mr gestures inheritence silliness. It uses your own mechanism (the GestureRecognizers list) so it's ready to implement.
There's a video and code examples.
I'll open source this and blog about it next week..
there are 2 things.
1. I have to currently add an extension method and call it to wire up the gestures, becasue you guys don't expose any hooks. Can you please add an AddRecognizer/RemoveRecognizer method to your IGestureRecognizer interface, so that you can communicate with our 3rd party gesture recognizers?
2. I have to use reflection to get to the renderers for views. Please please please please change this. I am doing some crazy powerful stuff with Xamarin, and the mechanism that allows me to do so many great things is getting access to a view's *current* renderer (i.e. not having to create it using Renderer.GetRenderer. If you open that up, it will make a lot of us who are pioneering, experimenting and really pushing the boat on what xamarin forms can do way more comfortable.
btw - the implementaiton is at the end of that forum post. To make life easier for you, here's the vid.
George's work is awesome, gesture support in a cross-platform way with Xamarin Forms is very much needed
Meanwhile, I did my own implementation too, screencast of a small demo here https://www.youtube.com/watch?v=utwawqSilGo
I would love to see this made possible in Xamarin Forms, along with an official mechanism to get hold of the renderer for a Xamarin Forms View / Page object.
I've just pinged support about this again. Months and no updates. Come on guys...
Putting my vote in for this too
Please implement this!
Thank you for taking the time to submit this feature request. We like this idea and have added it to our internal feature tracking system.
Xamarin Forms Team
Xamarin Team, We really need this right now please!
Any news on this bug? You have completed some of the work by exposing GetRenderer but the author (George Cook) still needs other workarounds such as ProcessGestureRecognizers. It's bad enough that you haven't added basic gestures for years now but you also obstruct other people's attempts by hiding your API.
By the way, George Cook's work is excellent. In addition to gestures he's also done another piece of your work - fast cells in list view. His examples at https://github.com/twintechs/TwinTechsFormsLib clearly show his cells are much faster than yours so you should definitely look into using his code instead.