-
-
Notifications
You must be signed in to change notification settings - Fork 26
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Fix annotations properties after mutating, update Google Maps to 2.1.…
…0, expose Map Styles (#51) * Prepare new 2.5.1 version * Attempt fix to update markers on position-changes * Fix possible memory-leaks, remove synthesize * Add back synthesize for markers to ease setters * Add back .travis to validate CI-test builds * Trigger .travis CI-build * Use locks to ensure thread-safety for annotations * Revert "Use locks to ensure thread-safety for annotations" This reverts commit 3b8c558. * Use 5.5.1.GA, remove locks, remove build.py * Fix annotations, update copyright * Update GoogleMaps iOS-SDK to 2.1.0 * Expose mapStyle property, bump to 2.6.0 * Update bundle files from Google Maps SDK 2.1.0 * Use UUID to identify markers * Use GCD to precent race-conds, fix autocomplete * Update example with autocomplete-configuration * Add address components to autocomplete result * Improve GCD * Update example file, fix GCD for kroll-thread * Fix latitude for legacy namespace
- Loading branch information
1 parent
963fb6d
commit 5f53010
Showing
214 changed files
with
495 additions
and
443 deletions.
There are no files selected for viewing
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
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
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
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
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
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
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
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
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
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
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
Oops, something went wrong.