Skip to content
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.

Sign up for GitHub

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

Jump to bottom

No way to get tapped coordinates on overlay #397

Open
zabojad opened this issue Mar 1, 2022 · 3 comments
Open

No way to get tapped coordinates on overlay #397

zabojad opened this issue Mar 1, 2022 · 3 comments
Assignees
@arriolac
Labels
priority: p3 Desirable enhancement or fix. May not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.

Comments

@zabojad
Copy link

zabojad commented Mar 1, 2022

Since PR 376, overlays from KML places are tappable.

It prevents the didTapAtCoordinate delegate method to be called when we've tapped an overlay. So that now, we cannot get the tapped coordinates at all when we've tapped an overlay.

Can we fix by either :

  • Control the overlays tappable value by passing a param somewhere (to the GMUGeometryRenderer constructor?)
    or
  • passing the tapped coordinates in the didTapOverlay method

?
@zabojad zabojad added triage me I really want to be triaged. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. labels Mar 1, 2022
@jpoehnelt
Copy link
Contributor

@zabojad Thank you for opening this issue. 🙏
Please check out these other resources that might be applicable:

This is an automated message, feel free to ignore.

@GuillaumeDgr
Copy link

Any fix on this ? Thks

@iHackSubhodip iHackSubhodip added the priority: p3 Desirable enhancement or fix. May not be included in next release. label Nov 9, 2024
@wangela wangela removed the triage me I really want to be triaged. label Nov 12, 2024
@wangela wangela mentioned this issue Nov 12, 2024
Closed
@dkati
Copy link

dkati commented Nov 13, 2024

we still need that fix

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@arriolac arriolac

Labels
priority: p3 Desirable enhancement or fix. May not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
7 participants
@arriolac @zabojad @jpoehnelt @wangela @iHackSubhodip @dkati @GuillaumeDgr