You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 21, 2023. It is now read-only.
I used the mapbox annotation plugin in one of my project and hit a limitation regarding the event manager. This plugin uses the following code on mapView to allow annotations to be draggable (as described here https://github.com/mapbox/mapbox-plugins-android/issues/884) :
mapView.setOnTouchListener { view, event -> ... }
But when a user wants to add its own detection system to add a functionality like custom drawing Mapbox example, he is stuck due to a limitation of the view which offer only one OnTouchListener. There exist a workaround consisting of adding another view on top of mapView to intercept the event but I think that there might be a better solution.
This issue could be resolved by adding a new interface to mapView which would allow to have multiple onTouchListener. I thought about something like this :
Hello,
I used the mapbox annotation plugin in one of my project and hit a limitation regarding the event manager. This plugin uses the following code on
mapView
to allow annotations to be draggable (as described here https://github.com/mapbox/mapbox-plugins-android/issues/884) :But when a user wants to add its own detection system to add a functionality like custom drawing Mapbox example, he is stuck due to a limitation of the view which offer only one
OnTouchListener
. There exist a workaround consisting of adding another view on top of mapView to intercept the event but I think that there might be a better solution.This issue could be resolved by adding a new interface to mapView which would allow to have multiple
onTouchListener
. I thought about something like this :Any thoughts and ideas are most appreciated 👍 @LukasPaczos, @tobrun and @tarigo
The text was updated successfully, but these errors were encountered: