hungio / route-me

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

moveToLatLong doesn't load tiles in new position when not cached #81

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Call moveToLatLong with a GPS location that is not cached
2. MapView will move to that location, and have the loading.png image as the 
tile.
3. Tiles will never load, loading image will stay forever.

What is the expected output? What do you see instead?
New tiles should be loaded from tile server.

What version of the product are you using? On what operating system?
Latest from SVN trunk.

This does not happen for a location where the tiles are cached. Reproducible on 
a number of 
devices.

Original issue reported on code.google.com by metroiph...@gmail.com on 11 Mar 2009 at 4:44

GoogleCodeExporter commented 8 years ago
Unable to reproduce, in a clean Simulator, with this test code using r293.

- (void)performTest
{
    NSLog(@"moving to Seattle");
    CLLocationCoordinate2D destination;
    destination.latitude = 47.62;
    destination.longitude = -122.35;

    [mapContents moveToLatLong:destination];
}

and within -applicationDidFinishLaunching add:
    [self performSelector:@selector(performTest) withObject:nil afterDelay:3.0]; 

Can you provide a sample failure case?

Original comment by halmuel...@gmail.com on 11 Mar 2009 at 7:25

GoogleCodeExporter commented 8 years ago
had a lightbulb moment, the moveToLatLong has to be done on the main thread, if 
the
call is made from another thread, the map will move, you can add markers etc, 
and if
the tiles are cached they will load. But it will not download new tiles. Not 
sure if
this is expected behavior or not. If so this can be closed.

thanks

Original comment by metroiph...@gmail.com on 11 Mar 2009 at 9:08

GoogleCodeExporter commented 8 years ago

Original comment by halmuel...@gmail.com on 11 Mar 2009 at 7:15