-
Notifications
You must be signed in to change notification settings - Fork 10
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
Make a distinction between swipe and tap #32
Comments
Unless I figure out how to get map guesture area from QtLocation ported to this plugin (#24), interaction is guided by https://github.com/rinigus/mapbox-gl-qml/blob/master/src/plugin/MapboxMapGestureArea.qml . Porting QtLocation map interaction was rather non-trivial. There is a lot of interaction between different components that are absent or replaced in this plugin. In particular, since this plugin is Mapbox GL centered, lots of abstractions were not needed. However, I would expect that lots of work has been done on Qt side to make it feel just right. So, I may try to look into it again and see if I can carry it over in some form. But it may take some time before I can look into it and I am not 100% sure I can do it in reasonable amount of time. Currently, probably the best would be to change MapboxMapGestureArea.qml in a way that such mixing would not occur. Should be possible, just would have to figure out how and what would be tolerances. Do you want to look into it? |
I could take a look at |
Good. Let's see who gets there first |
Currently when I tap, e.g. a POI icon on the map, the map usually moves a little bit, which I assume means that the tap is detected as both a swipe (pan) and a tap. It looks quite distracting. Can you make a distinction between these – some kind tolerance that a swipe has to cross? For comparison, QtLocation gets this right.
The text was updated successfully, but these errors were encountered: