search

MapXL / route-me

Automatically exported from code.google.com/p/route-me
0 stars 0 forks source link

Deceleration delegate call #85

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
Patch exists for declearation delegate calls

See:
http://groups.google.com/group/route-me-map/browse_thread/thread/e7f4c9ca6a681c6
3/99b7770879b51dcf?lnk=gst&q=om+map+decelerate#99b7770879b51dcf

not sure the status of it, but it would certainly provide needed delegate
calls.

Original issue reported on code.google.com by Quazie on 14 Mar 2009 at 7:36

GoogleCodeExporter commented 8 years ago 
the deceleration part of my patch works pretty good, it was the pinch delegate 
that
had issues.  I will break the patch into multiple commits to the branch (working
parts first), so that one can merge in just the working parts first until we 
fix the
pinch delegate.  My only warning is that the delegate names are most likely 
going to
change as we work through the code in this branch.  I am using these delegates 
in my
project currently with no real issues though, since after a pinch of one 
finger, the
map moves a bit and fires one of the other delegates (deceleration if I remember
correctly).

It is definitely useful to know when the map stops moving or is decelerated to 
0.  

I would eventually like to see one more delegate in this branch for
mapStartAcceleratedMove which fires only once at the beginning of a flick when 
the
map begins its animated move.  This method should also return the lat/lng of 
where
the map is -headed when it stops-.  This way I can start my asynchronous 
download as
the map is still moving.  This effect would be nice as the markers can be 
loaded and
drawn as the map is still headed to its eventual lat / lng.  In theory, when you
arrive at the endpoint, the markers will be waiting on you, which would be a 
really
nice timesaver and look a little magical / predictive.  It should be a simple 
bit of
math to figure out where the map will end up, but I think the trickiest part of 
this
idea would be firing this new delegate only once.  My only worry about this 
delegate
is firing it and then the load / redraw might slow down, or worst case stop, the
decelerated move.  Ideas or comments??

branches/issue85

Original comment by michaelh...@gmail.com on 18 Mar 2009 at 1:41

GoogleCodeExporter commented 8 years ago 
mapViewDidEndDecelerating: RMMapView
mapViewDidMove:RMMapView toLatLon:CLLocationCoordinate2D
mapViewDidEndPinch:RMMapView

Those are my suggestions.

Original comment by Quazie on 18 Mar 2009 at 3:55