Form like callout, touch events forwarding. about calloutview HOT 6 CLOSED

OK, so this was pretty tricky but I think I figured it out. On iOS 6, MKMapView uses a UIGestureRecognizer to figure out when you've tapped on the map. For some reason, when you attempt to click a UITextField in the callout, this causes the gesture recognizer to fire and the map view to think that you've clicked outside the pin and wish to dismiss the callout.

I've just pushed an example to the master branch that demonstrates how to work around this. The trick is to subclass MKMapView and override the gesture recognizer delegate to swallow touches from UIControl subclasses. Just uncomment the three lines that create a UITextField to see it in action.

Hope this works for you!

from calloutview.

Still no luck, could the problem be caused by AutoLayout and/or using much larger view than standard callout created from a nib which also uses auto layout? As well I also have a long press attached to the map.

I noticed that I in that overridden delegate method for gesture recogniser, the touch.view is always MKAnnotationContainerView

I did some printing in the debugger.

http://pastebin.com/GCjd58p5

why does the callout view have negative x/y?

from calloutview.

Ok, so main the difference between how your sample code works and what happens when I tap the map in code, is precisely, what is under touch.view. In your case it is indeed what I clicked, button/textfield/etc. In my code its ALWAYS that MKAnnotationContainerView no matter what I click. The weird part, I am pretty much not doing anything else than whats in the sample project.

from calloutview.

Hm, that's weird. So how did you fix it?

from calloutview.

http://pastebin.com/vLuhB8dx

Turns out that altering -pointInside:(CGPoint)point withEvent:(UIEvent *)event inside SMCalloutView by adding
contentViews pointsInside method to be also checked, does the job perfectly. I am not sure if I removed this line before by myself. But it works now.

from calloutview.

Yeah, I should have explicitly mentioned that, but that was one of the things I fixed when looking into this originally. Glad that did the trick!

from calloutview.