Only Process Most Recent Location #346
Merged
+4
−2
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@jamesmontemagno Is there any way to get this linked to issue #332 ? Linked issues is disabled for me, presumably because I don't have write access to this repo. Also, is there anything missing that is causing this PR to not be reviewed? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Please take a moment to fill out the following:
Fixes #332
Changes Proposed in this pull request:
-Apple's
-(void)locationManager:(CLLocationManager *)manager didUpdateLocations:(NSArray *)locationsmethod declared byCLLocationManagerDelegateinputs an array of locations where the last location is the most recent. Previous locations in the array may be older, therefore we should only process the last one.