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 Aug 8, 2023. It is now read-only.
getMarkerViewsInBounds() method returns all the MarkerView annotations irrespective of LatLngBounds being passed.
I need to do markerHitTest to see if a user tapped point falls on any MarkerView. Because of getting all MarkerViews, I cannot use this method.
P.S : This also causes invalidateViewMarkersInBounds() not do anything as the above method will always return all the MarkerViews. But I can see the contains check was intentionally removed to fix #5402 .
cc @tobrun Looks like I have to wait till #4522 is resolved ?
Steps to trigger behavior
Ask getMarkerViewsInBounds(latLngBounds);
All MarkerViews are returned even if they are outside bounds.
Expected behavior
Only MarkerViews within bounds should be returned
Actual behavior
All MarkerViews are returned even if they are outside bounds.
The text was updated successfully, but these errors were encountered:
We've removed getMarkerViewsInBounds() in the 4.2.0. Two solutions for this could be using the new query map features introduced (see #5165) or a better option might be using the Turf inside method found in mapbox-java (also included in the maps SDK).
getMarkerViewsInBounds() method returns all the MarkerView annotations irrespective of LatLngBounds being passed.
I need to do markerHitTest to see if a user tapped point falls on any MarkerView. Because of getting all MarkerViews, I cannot use this method.
P.S : This also causes invalidateViewMarkersInBounds() not do anything as the above method will always return all the MarkerViews. But I can see the
contains
check was intentionally removed to fix #5402 .cc @tobrun Looks like I have to wait till #4522 is resolved ?
Steps to trigger behavior
Expected behavior
Actual behavior
The text was updated successfully, but these errors were encountered: