This repository has been archived by the owner on Aug 8, 2023. It is now read-only.
Remove mention of sprite atlas limitation from iOS points guide #9258
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
The total size of the sprite sheet is no longer limited as it was before. This change updates the guide that helps developers choose between the different annotation mechanisms.
1ec5
added
annotations
jfirebaugh
approved these changes
Jun 13, 2017
|
The Android build failure is unrelated, per #9257 (comment). |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The total size of the sprite sheet is no longer limited to the extent that it was before, now that #9213 has landed, fixing #3185. This change updates the guide that helps developers choose between the different annotation mechanisms, removing the sprite atlas limitation from the list of cons for MGLPointAnnotation. (In fact, this was also a limitation of the runtime styling approach, but we neglected to mention that.)
/cc @ericrwolfe @jfirebaugh