-
-
Notifications
You must be signed in to change notification settings - Fork 37
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
Is there way to combine flutter_map_marker_popup and flutter_map_dragmarker? #40
Comments
Heya, tbh I don't know enough of the popup plugin to help really. I can't remember exactly about the onPan vs onVert/Hor, I have a feeling there was a conflict with the gesturehandler and onPan, but I may well be remembering that wrong, it was a long time ago |
Do you have any solution to open a Popup or similar to your DragMarkers? Maybe way to hook onto onTap or something? |
Well, you can certainly pass a func to onTap parameter I guess, I'm not sure if that would help ? |
@S-Man42 Did you make a solution? |
Unfortunately, not yet. For my hotfix I downgraded the Flutter Map library version and then it worked again. But this cannot be the final solution |
Previously I implemented my draggable marker on my own. So I was able to react on the tap to open a popup using the PopupMarker plugin.
Since their update from v3 to v4 the
onPanUpdate
is not called anymore (funny enough: all other events still work asonVerticalDragUpdate
).I tried to implement the
onVerticalDragUpdate
andonHorizontalDragUpdate
instead as you did, but it worked not as expected. I only was able to drag the marker in exact horizontal and vertical direction. Reading your code did not make it clear to me how you bypassed this behaviour to enable panning in all directions, unfortunately. (Moreover it seems to me more like a dirty workaround to use these two events instead the plainonPanUpdate
, which worked quite well all the time...)However, I tried to integrate your plugin directly but I am not sure how to keep the popup functionality because both plugins are different kind of layers...
Do you see a way around this?
The text was updated successfully, but these errors were encountered: