-
Notifications
You must be signed in to change notification settings - Fork 2.2k
[ASMapNode] bug fixes + added the ability to zoom in on the annotations + example project #1792
Conversation
…hive#1753) [ASMapNode] Change map snapshot when updating it with a new region (facebookarchive#1754) [ASMapNode] Commented out code that is causing inaccurate behavior [ASMapNode] Added the ability to zoom in and show annotations, similar to showAnnotations:animated: of MKMapView. Added a basic example for ASMapNode to try out the different changes
Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. In order for us to review and merge your code, please sign up at https://code.facebook.com/cla - and if you have received this in error or have any questions, please drop us a line at cla@fb.com. Thanks! |
Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Facebook open source project. Thanks! |
options.scale = oldOptions.scale; | ||
options.region = region; | ||
self.options = options; | ||
// self.options.region = region; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What's the motivation for this change?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh I see, it's to trigger a new snapshot. Hmm. Let's use [self.options copy]
instead.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@george-gw yes, @Adlai-Holler is right - we should copy the options, then just write to the region value, and set it back to self.options.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@appleguy @Adlai-Holler I had written it with [self.options copy]
before, but it didn't work for some reason, that's why I did what I did there. But I must have done something wrong somewhere else because it seems to work fine now with [self.options copy]
.
Thanks!
Looks like a number of revisions are required here. Thanks for contributing, @george-gw! This is an important component, so we should get at least two ASDK accepts to land. |
@appleguy I fixed everything except setting Thank you for the revisions and this library! |
@Adlai-Holler @maicki - time for a 2nd review on this. |
Would you be willing to protect the new Once that is in, 👍 from me! |
@Adlai-Holler: Wouldn't it potentially cause a problem in PS: I added the lock |
That's odd! Why would the test fail based on the new commit? |
@george-gw It should be OK because it's acceptable for the main thread to wait on background threads. Strange that an arbitrary ASDisplayLayer test failed. I've restarted the tests – let's see if the failure occurs again. @appleguy @hannahmbanana Maybe we have a fragile test? Here's the failure:
|
@Adlai-Holler Alright, cool! And thanks for restarting the test, seems good now! |
Thanks for following through on this one @george-gw ! Glad to have this in. |
I enjoyed the collaboration, thank you for your input @Adlai-Holler :) |
A minor change: Fixed typo in some comment