-
Notifications
You must be signed in to change notification settings - Fork 1.3k
[android] #2588 - Make getTopOffsetPixelsForAnnotationSymbol private. #2592
Conversation
e490829
to
df92362
Compare
@@ -84,7 +89,7 @@ public boolean isVisible() { | |||
} | |||
|
|||
public MarkerOptions position(LatLng position) { | |||
((Marker)annotation).position = position; | |||
((Marker)annotation).setPosition(position); |
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.
This will cause breakages with JNI as described in #2551.
@bleege That's what I thought, but it didn't seem to break JNI? Also it's not that change that would break, it would be changing the inner fields of Marker, JNI doesn't use the functions. I tested it both with the |
Also noting that this fixed a bug in Going to do another test with full |
df92362
to
67f0108
Compare
Did more testing, JNI does not break. I can add and remove markers fine along with InfoWindows. |
Node is failing for some reason. As this is Android only change, merging. |
@bleege Yeah looked like it, @mikemorris opened that after I came across it. I did try restarting the job several times keep hitting same node error. |
Node.js v4.2.1 landed today, should be all fixed now @ljbade |
@mikemorris Thanks! |
Make getTopOffsetPixelsForAnnotationSymbol private
Also:
captures/
to .gitignore
setPosition
getSprite()
sprite
/position
private
now that above bugs are fixed (JNI still can directly access the field)