Marker refactoring about route-me HOT 3 OPEN

I remember there were questions about performance issues if there is a lot of markers on the map. But if the loss is acceptable it would be great to have views instead of layers as touch event handling on makers is now very awkward !

from route-me.

We'd definitely need to incorporate some kind of marker view reuse, I'd say, if we were going to use UIViews - the same way MapKit does it, I guess.

That said, I'd be interested in finding out what the end goal is, here - what kind of interaction are we after, with markers?

For marker dragging, the current implementation is totally broken, and wouldn't be fixed by making markers UIViews - we need to track drag operations from the superview, so that when fast movements result in the touch leaving the bounds of the dragged marker, the drag doesn't end. I've implemented this in an RMMapView subclass in my own project, and it works fine, with CALayer markers.

For marker selection, I'd imagine the better way to implement it would be also based in the superview - determine which markers are under the touch, and select the one that's closest. A UIView wouldn't help there, either. (In fact, I re-implemented this in MapKit, because MapKit doesn't do it right either - and I implemented it in a superview of the MKMapView)

For callout views, which is the other use I can think of for marker interaction, I just create a subview of RMMapView which I keep anchored to the marker via the map move and marker move delegate methods.

from route-me.

PS some more discussion on this issue here - discussion didn't get copied over with the issue tracker migration, unfortunately.

from route-me.