Sunday 15 March 2015

cllocationmanager - Managing LocationManager didUpdateLocation -


Two questions:

  1. Location Manager is. When I run the code below, this cycle has started. I suspect that there is a depth of the processor and the espionial battery. When you have accurate enough improvements, what is the accepted method to kill this loop?

  2. Can I customize it to return to longitude / latitude (long / lat)?

    Int degree = newLocation.coordinate.latitude;

    Dual decimal = fibers (new position. Cordinate.latititude - degrees);

    int min = decimal * 60; second seconds = decimal * 3600 - min * 60;

    NSString * lat = [NSString stringWithFormat: @ "% d °% d '% 1.4f \" ", degree, minute, second];

    NSLog (@" Current Latitude :% = ", Latitude);

    degrees = newLocation.coordinate.longitude;

    decimal = fab (new location

    seconds = decimal * 3600 - minute * 60;

    NSString * longt = [suspicious long-degree - degree];

    minutes = decimal * 60 * NSString stringWithFormat: @ "% d °% d '% 1.4f

    }

    / P>

    1) When you are in place with the necessary accuracy Just click on [manager stopUpdatingLocation]; Method in locationManager: didUpdateToLocation: fromLocation: .2). Coordination (consisting of latitude and longitude), you can define a property, @property CLLocationCoordinate2D myCoordinate; Which is called locationManager: didUpdateToLocation: , and there on itself Microdinate = new location.Cordinate ;

No comments:

Post a Comment