Taps aren't firing on the right markers

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Have a few markers clustered close together on the map
2. Tap on one of them, either the tap doesn't fire, or it fires on the
wrong marker.

What version of the product are you using? On what operating system?
rev 163. This defect has been around for at least a month.

Original issue reported on code.google.com by pspda...@gmail.com on 13 Dec 2008 at 8:08

[GoogleCodeExporter]

Original comment by davigoli@gmail.com on 13 Dec 2008 at 10:37

• Changed title: Taps aren't firing on the right markers

[GoogleCodeExporter]

This is closely related to issue 59, just raised. The problem is that the whole 
size of the marker image is 
regarded as the touch area, whereas users expect only the non-transparent 
non-shadow part of the marker 
image to accept the touch.

Original comment by john.e...@gmail.com on 2 Mar 2009 at 4:34

• Changed state: Accepted

[GoogleCodeExporter]

recent changes in the issue 59 branch should make it possible to fix this issue 
for specific marker images, by 
setting an appropriate touchAcceptRegion (a rect).

In addition, the concept of focus has been added, which ensures that the most 
recently tapped marker gets taps 
in preference to other nearby markers.

Original comment by john.e...@gmail.com on 4 Mar 2009 at 5:28

[GoogleCodeExporter]

Original comment by john.e...@gmail.com on 6 Mar 2009 at 9:33

• Changed state: Started