iOS: leftButton not always responding to click

[m1ga]

The leftButton is not always responding to a click. It sometimes stays in the "clicked" position too.

Steps to reproduce:

• run the example below
• click on the pin
• click on the leftButton icon
• watch the log output
• clicking the infobox works everytime

var Map = require('ti.map');
var win = Titanium.UI.createWindow();

var mountainView = Map.createAnnotation({
	latitude: 37.390749,
	longitude: -122.081651,
	title: 'Appcelerator Headquarters',
	subtitle: 'Mountain View, CA',
	leftButton: Ti.UI.iOS.SystemButton.INFO_LIGHT,
});

var mapview = Map.createView({
	mapType: Map.NORMAL_TYPE,
	region: {
		latitude: 37.390749,
		longitude: -122.081651,
		latitudeDelta: 0.01,
		longitudeDelta: 0.01
	},
	animate: true,
	regionFit: true,
	userLocation: true,
	annotations: [mountainView]
});

win.add(mapview);

var clickCounter = 0;
mapview.addEventListener('click', function(event) {
	Ti.API.info(clickCounter + ': clicked ' + event.clicksource);
	clickCounter++;
});
win.open();

[zenjoe]

It affects leftButton, rightButton, leftView and rightView (testet on 11.1.1 GA)

[m1ga]

@hansemannn did you have time to look at this issue?

[hansemannn]

I oversaw it, sorry! Will schedule to complete this month

[hansemannn]

To understand this correctly: The accessories leftView/rightView & leftButton/rightButton were also in the "click" event of the map view? How were they distinguished from the normal click events?

[m1ga]

I think they'll returned e.g. rightButton or leftView as clicksource. There was an older ticket #104 (point 3) where the same issue was in 2015.

I've only created the ticket for a Slack user (can't find it because it's too old) but we have another thread about it too

[ferdi2005]

That slack user is me! @m1ga

[hansemannn]

Okay, so I've spent some time on this, but couldn't find any issue with the code, yet. Though I am sure to know what could cause it: The click listener is currently handled via the "global" map click event of the map, which may not always respond to child views of the annotations. When looking into other native implementations, they use a tap gesture recognizer for the button / view itself, which is much more flexible, also in terms of advanced tap gestures like "longpress" and "singletap".

I will try to refactor the code to use these gesture recognizers instead and start clean. The ti.map module has a LOT of legacy code that should be cleaned up.

[LynMajor]

I'm having this issue also, on iOS 16.3.1 and Ti.Map v7.0.0 click source never returns 'leftButton' or 'rightButton' but is working for 'infoWindow'

Is this likely to be fixed?

Many thanks Lyn

[hansemannn]

I am seriously considering to rewrite ti.map completely in Swift to start fresh for things like this. Any thoughts if it's worth it?

[LynMajor]

I am seriously considering to rewrite ti.map completely in Swift to start fresh for things like this. Any thoughts if it's worth it?

Hi Hans, We use the map module in two apps both iOS and Droid and apart from this issue it seems to work to an acceptable level. I would assume that its a popular module but guess you would need to ask the community.

[zenjoe]

Same problem - but solved it by sliding in options into the view I usually would attach to left/right button. (Like - calculate route, more info and stuff. But yeah - would be great with an update to the module :)