Assigned
Status Update
No update yet.
Comments
mu...@gmail.com
We prefer to have a smaller Marker Click Area. It would be good to have an API that will adjust this marker clickable area or even a workaround.
A comment was added to issue #5368. Based on the comment, I opened a new issue to facilitate adjustable click area.
Appreciate your help.
A comment was added to issue #5368. Based on the comment, I opened a new issue to facilitate adjustable click area.
Appreciate your help.
mu...@gmail.com
Also, I tested with my own icon for size 48*48dp. The click area goes outside of 48*48dp area.
Note: I created mutiple png files to match .75:1:2:3:4 ratio. Base line (mdpi) is 48*48 dp.
User expects omMarkerClickListener to work nly when marker is clicked and not when the click area is in close proximity to the marker.
Note: I created mutiple png files to match .75:1:2:3:4 ratio. Base line (mdpi) is 48*48 dp.
User expects omMarkerClickListener to work nly when marker is clicked and not when the click area is in close proximity to the marker.
ad...@google.com
Thanks for the detailed report. The way it currently works is by design but I can appreciate the arguments for allowing the clickable area to be customized.
For a bit of background about we actually currently do some smart things around Markers and clicking that are similar to how the Google Maps application works (this behavior might be modified in the future):
- We search in a radius around the point that was reported as tapped. This is because touch screen users don't use a precise pointer like a mouse to tap, but use a fat fuzzy finger. Hence a tap on the screen is generally intended to cover a region of the screen and not just a single point. While this becomes less important for larger markers, it's very important for small markers (we call them measles!).
- When tapping on an area with overlapping markers, we actually iterate through the markers when the same point is tapped repeatedly.
- If you have so many areas with overlapping markers, a clustering approach is advised. There are a number of open source libraries available for this (e.g.,https://github.com/googlemaps/android-maps-utils/tree/clustering , https://github.com/twotoasters/clusterkraf , https://code.google.com/p/android-maps-extensions/ ).
For a bit of background about we actually currently do some smart things around Markers and clicking that are similar to how the Google Maps application works (this behavior might be modified in the future):
- We search in a radius around the point that was reported as tapped. This is because touch screen users don't use a precise pointer like a mouse to tap, but use a fat fuzzy finger. Hence a tap on the screen is generally intended to cover a region of the screen and not just a single point. While this becomes less important for larger markers, it's very important for small markers (we call them measles!).
- When tapping on an area with overlapping markers, we actually iterate through the markers when the same point is tapped repeatedly.
- If you have so many areas with overlapping markers, a clustering approach is advised. There are a number of open source libraries available for this (e.g.,
mu...@gmail.com
Thank you for the reply.
Perhaps you could enable the ability the adjust the "radius" around the point that was reported as tapped. Say (for example), a "weight" attribute on Marker 0 means the (radius) hit-area is the default, 0.75 means a reduction by 25% area, 0.5 means reduction by 50% etc., Just a thought as the ability to adjust the marker click-able area can value-add to us.
Hope you could add to the enhancement list at your end :-)
Perhaps you could enable the ability the adjust the "radius" around the point that was reported as tapped. Say (for example), a "weight" attribute on Marker 0 means the (radius) hit-area is the default, 0.75 means a reduction by 25% area, 0.5 means reduction by 50% etc., Just a thought as the ability to adjust the marker click-able area can value-add to us.
Hope you could add to the enhancement list at your end :-)
[Deleted User] <[Deleted User]>
Adjustable click area is very appreciated because currently it is not possible to disable marker clicks and handle it by the map. Setting dummy OnMarkerClickListener which returns "true" in conjunction with setting marker click area to "zero" will solve this problem.
Seehttp://stackoverflow.com/questions/15401988/disable-onmarkerclicklistener-completely-in-maps-api-v2#comment22172550_15401988 for another discussion.
See
ja...@gmail.com
I am having same issue?
Does any one found solution for this?
Does any one found solution for this?
jt...@gmail.com
+1, this is very needed for the reason mentioned in http://stackoverflow.com/questions/15401988/disable-onmarkerclicklistener-completely-in-maps-api-v2 .
I need more granular control over which marker is clicked when they click on the map, so I need to use the map click event instead of the marker click event. Unfortunately, there is no way to disable the marker click event and just handle all map click events. If you have the marker click event call the map click event, you can only pass in the selected marker's position, which is NOT necessarily where they clicked, due to the larger radius logic.
I need more granular control over which marker is clicked when they click on the map, so I need to use the map click event instead of the marker click event. Unfortunately, there is no way to disable the marker click event and just handle all map click events. If you have the marker click event call the map click event, you can only pass in the selected marker's position, which is NOT necessarily where they clicked, due to the larger radius logic.
ne...@gmail.com
Same problem, somebody has a solution ???
The click area is larger than the marker icon displayed, so when 2 markers are next to, click on one displays info window of the other !!
The click area is larger than the marker icon displayed, so when 2 markers are next to, click on one displays info window of the other !!
an...@google.com
sh...@gmail.com
Some related features I think would be useful:
1) We should be able to declare a marker non-clickable. So that it is ignored when a user clicks on an area with overlapping markers. This would prevent a confusing user experience when markers that are just for display are next to markers that have a functional use, because the marker for display wouldn't prevent the functional marker from being clickable every other click.
2) I think you should be able to set the Map to be non-clickable. This is because I found if you click a marker 2 times. It will click the marker the first time, then trigger the map clicked event which would be confusing to the user because they tapped the marker twice.
3) If we want to make a marker clickable. We should be able to set the clickable area to be the area the marker icon actually covers. So the marker being near other markers is not an issue or confusing to the user.
1) We should be able to declare a marker non-clickable. So that it is ignored when a user clicks on an area with overlapping markers. This would prevent a confusing user experience when markers that are just for display are next to markers that have a functional use, because the marker for display wouldn't prevent the functional marker from being clickable every other click.
2) I think you should be able to set the Map to be non-clickable. This is because I found if you click a marker 2 times. It will click the marker the first time, then trigger the map clicked event which would be confusing to the user because they tapped the marker twice.
3) If we want to make a marker clickable. We should be able to set the clickable area to be the area the marker icon actually covers. So the marker being near other markers is not an issue or confusing to the user.
sp...@gmail.com
On iOS, the clickable areas of the markers are exactly matching the custom bitmap dimensions, users won't misclick. On Android, my app users reported that they always misclicked.
I prefer to have the same click behavior as Google Maps SDK for iOS, or let us disable onMarkerClick event completely, then we can implement our own behaviors using onMapClick event.
I prefer to have the same click behavior as Google Maps SDK for iOS, or let us disable onMarkerClick event completely, then we can implement our own behaviors using onMapClick event.
ak...@gmail.com
Being able to make a marker non-clickable would be a very useful first step. This can already be done on iOS:
https://developers.google.com/maps/documentation/ios-sdk/reference/interface_g_m_s_overlay#a45005ec17da8c14bd1978f5cf19d91c7
Without this, certain useful features are not possible. For example, displaying a custom blue dot on the map as a marker eats any clicks near the user's current location.
Without this, certain useful features are not possible. For example, displaying a custom blue dot on the map as a marker eats any clicks near the user's current location.
[Deleted User] <[Deleted User]>
Is it somehow possible to disable ` - When tapping on an area with overlapping markers, we actually iterate through the markers when the same point is tapped repeatedly. ` functionality?
Im already handling this with changing zindex manually. now I want to disable this "Smart functionality"
Im already handling this with changing zindex manually. now I want to disable this "Smart functionality"
jh...@google.com
an...@google.com
an...@google.com
na...@gmail.com
Can you tell by when can we expect this to be solved? I have a HeatMap below the markers where the user can click and data is loaded as per onMapClick method. My custom marker hijacks the click currently in nearby areas.
dm...@gmail.com
+1
th...@gmail.com
+1
an...@google.com
zo...@gmail.com
Hi Google, any news? It's been over 5 years now...
[Deleted User] <[Deleted User]>
+1
ra...@gmail.com
hacking emergency helpline
ygsbtvfcegty6fbdg
ALL GOD CREATIVITY
ygsbtvfcegty6fbdg
ALL GOD CREATIVITY
cr...@gmail.com
Any news or workaround?
jh...@google.com
ma...@gmail.com
As mobile developers, we always expect the Google SDKs to work same in both iOS and Android. iOS developers are not facing this issue. why Android developers?
mi...@gmail.com
Anything new?
[Deleted User] <[Deleted User]>
Hi everyone I
jo...@gmail.com
I found a way to workaround this issue. See my stackoverflow answer: https://stackoverflow.com/a/58140323/1499750
j2...@gmail.com
guys take this out ..its annoying ..we have custom markers and there close together and your causing different click events to get fired.... this should be a top priority to remove it.
gi...@gmail.com
Please fix this issue
[Deleted User] <[Deleted User]>
+1
bw...@gmail.com
+1
ar...@gmail.com
+1
so...@gmail.com
from flutter +1
ce...@gmail.com
+1
mi...@gmail.com
+1
pc...@gmail.com
+1
gi...@gmail.com
Hello, this issue happens not just when 2 markers are overlapping but also when they are just close to each other. What is the proximity value between 2 markers, at which comparison by zValue is triggered? And can that value be changed from our side? Thank you!
Video showing the issue attached and can be viewed here also:https://www.dropbox.com/s/d24m1mkx8ryyd56/mobizen_20201215_203921.mp4?dl=0
Video showing the issue attached and can be viewed here also:
ma...@gmail.com
+1 Please fix. We are trying to use overlapping marker z-index cycling without showing the info window. Why should that be so difficult?
gi...@gmail.com
This is not a "Feature Request" but a serious bug that only appears on Android. On iOS and Web your SDK works perfectly. How can you care less about your own Android platform?
[Deleted User] <[Deleted User]>
+1
ch...@siteplan.at
+1
ma...@gmail.com
+1
ab...@gogoro.com
+1
le...@gmail.com
+1
ch...@monstar-lab.com
+1 This is a serious bug, really
rr...@gmail.com
Still present
da...@gmail.com
+1 Please fix this. Customized clickable area is relevant when the markers density is high. on a map
to...@gmail.com
Any update on the issue?
This bug makes using the map a chore for our users.
This bug makes using the map a chore for our users.
to...@lovoo.com
This bug creates horrible user experience for us also. Users cannot interact with the map with other features because markers click listeners are triggered. Any update on that after 10 years?
ig...@gmail.com
+1
wi...@gmail.com
Comment has been deleted.
to...@gmail.com
I missed the 10th anniversary.
Happy Birthday you little Bug!
Happy Birthday you little Bug!
lo...@gmail.com
Is the assignee still working at Google?
ro...@funda.nl
+1
gi...@gmail.com
This issue is amplified as more pins are showing on the map. It's 10 years already, this is ridiculous
no...@vivasoftltd.com
Google is dead :)
ta...@gmail.com
> From
Yes, it's duplicate ofhttps://issuetracker.google.com/35823783 which was created in 2013. It seems google is not interested in resolving this issue with android maps. It's been 10 years but issue is still there. In iOS SDK it works fine then why it's not working in Android SDK.
It's request please resolve this issue ASAP.
Yes, it's duplicate of
It's request please resolve this issue ASAP.
mi...@gmail.com
+1
ga...@gmail.com
+1
mo...@gmail.com
+1
zh...@gmail.com
+1
dr...@gmail.com
+1
ar...@gmail.com
+1
Description
2. Create OnMarkerClickListener(). See attached file for the code. Uses "default" marker and not any custom bitmap. Refer attached code for adding Marker.
3. Run the App.
4. Add Markers by clicking on the map. You an add mutiple markers as the onClick adds the marker on the map.
5. Click on any of the "added" Marker(s). You should see a toast message
6. Click on the area just outside of the marker and you will notice onMarkerClickListener gets fired and toast message is being displayed.
Looks like the clickable area for Marker is too wide. Also, I noticed an issue #5368 and not sure whether it is related to this issue but is closed.
How can we control "marker clickable area"? Is it a bug or the expected behavior? I understand there should be hit-area around the marker to sense the touch gesture but this hit-area is too wide in the given example. Is there a way to control the size of the hit-area for the Markers in Google Android Maps v2? Our users need an adjustable click are on the Markers.
Thank you,
*********************************************************
For developers viewing this issue: please click the 'star' icon to be
notified of future changes, and to let us know how many of you are
interested in seeing it resolved.
*********************************************************