-
Notifications
You must be signed in to change notification settings - Fork 33
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
Duplicate points of interests when zooming #582
Comments
I have seen this happen from time to time, I could not understand when and why it starts. |
I was able to reproduce the issue using a scenario similar to this one:
@MatanBenMoshe, FYI. |
Related check-in is to reverse the order of changing a base-layer - first we add the new layer and then remove the previous, I think this might explain this issue as the cluster layer doesn't work well when there's no base layer, I think... |
I'm publishing a fix tonight for this issue, I was somewhat able to reproduce it, although I'm not sure this is the only scenario which causes the bug. |
The issue was not solved using the code changes I made.
|
@nadavheimann @MatanBenMoshe I'll publish tonight a fix to this issue, hopefully will put this issue behind us once and for all. |
Published. |
Thanks, I will check later
…On Mar 1, 2018 09:24, "Harel M" ***@***.***> wrote:
Published.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#582 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AEu4hi2UjdRWhgCDnF_9mbbRSDQD6Je-ks5tZ6JEgaJpZM4ROQgE>
.
|
The problem happen again. |
I need to be able to reproduce the scenario in order to do something with your report... |
I hide and show some times the route layers and then when I move the map or zoom it the points duplicate. |
Yes, this is how I originally discovered this issue, but after the fix I made I didn't saw it happen again. |
i have multipal interest point on same point
look at the attachment
its same problem at all points
The text was updated successfully, but these errors were encountered: