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.

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

[BUG] Map callbacks with coordinate arguments do not work correctly when invoked on 'non-primary' world #2008

Closed
JaffaKetchup opened this issue Jan 8, 2025 · 1 comment · Fixed by #2025
Assignees
Labels
P: 2 (soon™?) S: core Scoped to the core flutter_map functionality

Comments

@JaffaKetchup
Copy link
Member

What is the bug?

The onTap (and probably the rest of the handlers in MapOptions) callback in the Markers page in the example does not add the marker to the location tapped, if that location is not in the main world. It adds it to the closest point in the main world.

See #2000 (review).

Note that this bug does not yet exist in a released version.

How can we reproduce it?

Zoom out in the Markers example, so that a world is not the main 'focus' (centered) in the view. Tap to add a marker to this world. It is added along the anti-meridian at the same latitude, in the main world.

Do you have a potential solution?

No response

Platforms

All (unreleased)

Severity

Minimum: Allows normal functioning

@JaffaKetchup JaffaKetchup added bug This issue reports broken functionality or another error P: 2 (soon™?) S: core Scoped to the core flutter_map functionality labels Jan 8, 2025
@JaffaKetchup JaffaKetchup removed the bug This issue reports broken functionality or another error label Jan 18, 2025
@monsieurtanuki
Copy link
Contributor

I'll have a look at it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P: 2 (soon™?) S: core Scoped to the core flutter_map functionality
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants