Ok, it seems that a map view looses its click event listener\nafter the location changes. The attached project demonstrates\nthis.
I had a similar problem where I wasn't able to get any events on\na map view. A child view added to a map view would get a click\nevent, but not the map view itself. I documented this behavior\nhere.
\n\nhttp://developer.appcelerator.com/question/32451/mapview-ignoring-t...
This is a duplicate bug and should have been fixed, but I cannot\nget the provided test to work. A simpler test needs to be provided.\nMap views do not receive click events except when a pin is\nselected.
\nI am unable to duplicate the behavior and I believe this was\nfixed as part of an earlier map view bug. Leaving open until I can\nconfirm this.
Still waiting on a simpler example.
run Map View test in KS - click on map - no logging occurs\n(click event is not fired)
Pushing out again.
A pro client is interested in this fix now as well.
\nThe following demonstrates the problem. Click on the annotation,\nand you will see the map's click event fires and an alert is shown.\nClick anywhere else, and nothing will happen.
\n\nvar win = Ti.UI.createWindow({ backgroundColor: '#fff' });\n\nvar map = Titanium.Map.createView({\n annotations: [Titanium.Map.createAnnotation({\n latitude: 37.390749, longitude: -122.081651,\n title: 'You Clicked Me!'\n })],\n region: {\n latitude: 37.390749, longitude: -122.081651,\n latitudeDelta: 0.01, longitudeDelta: 0.01\n }\n});\nmap.addEventListener('click', function () {\n alert('Map Clicked!');\n});\n\nwin.add(map);\nwin.open();\n\n(from [5facf6d39cd9f693da29eab4548a651bf3f3f77d])\n[#1104] Fix to provide click-on/click-off for\nuser-defined annotations. \nhttps://github.com/appcelerator/titanium_mobile/commit/5facf6d39cd9...
A full fix for this actually requires a guarantee of iOS 3.2+\nrunning on device. Extensive research has shown that Apple does not\nprovide a way to intercept events on a map view in 3.1.x without\nusing undocumented classes or features.
\nThe previous commit is a slap patch to ensure that it is\npossible to detect when somebody \"clicks off\" an annotation. This\ncan be done by checking the \"source\" property.
Forgot to mark \"in-progress\" as well. A full fix will be\nprovided if possible.
Slap patch addresses customer issue. Going to bump the remainder\nof the bug (generic 'click' events) to TBS 1.7 so that we can\ndiscuss with the Android team about whether or not to break them\nand replace the name with something much more sensible.
Had a brief conversation with Marshall, we have parity on iOS\nand Android (only detect clicks on map overlays, i.e. pins and\nannotations). iOS has the addition of checking to see if you click\nOFF of either of these things and back on the map because that was\na feature request.
\nSo, consider this resolved for iOS. We will not support\ngeneral/generic 'click' events on the map.
On Android, I don't see the click event firing if the background\nof the annotation is clicked.
\nUsing this code, you might see 'title' in the info message (if\nyou actually click the title element) but you won't see\n'annotation'. The reason this is important is because a user might\nfail to click through to another page if they happen to miss one of\nthe elements in the annotation.
\n// this sets the background color of the master UIView (when\nthere are no windows/tab groups on it)\nTitanium.UI.setBackgroundColor('#000');
\nvar win = Ti.UI.createWindow({ backgroundColor: '#fff' });
\nvar map = Titanium.Map.createView({
\n mapType: Titanium.Map.STANDARD_TYPE,\n animate: true,\n regionFit: true,\n region: {latitude: 37.390749, longitude: -122.081651,latitudeDelta: 0.01, longitudeDelta: 0.01 }\n\n});
\nvar myAnot = Titanium.Map.createAnnotation({
\n latitude: 37.390749,\n longitude: -122.081651,\n title: 'You Clicked Me!',\n pincolor: Titanium.Map.ANNOTATION_PURPLE,\n animate: true\n});\n\nmap.addAnnotation(myAnot);
\nmap.addEventListener('click', function(e) {
\nTitanium.API.info(e.clicksource); });
win.add(map);
\nwin.open();
Assigning to Don so that we can get an Android ticket requesting\nfeature parity.
Actually, scratch that. Going to make a new ticket for Android\ninstead. Durr.
added release-1.7.0 tag.