-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Android Camera API #3244
Comments
Related to #2805 |
Basic classes, method stubs, and a TestApp activity are built. The next step is wiring up Core GL to the method stubs and verifying via TestApp activity. |
…uilding MapView's getCameraPosition() and animateCamera().
…g zoom level of CameraActivity a bit more obvious
…CameraActivity to support 3 use cases to align with the 3 animateCamera methods.
I refactored the CameraActivity in the TestApp to provide a visual test harness for the 3 |
Confirmed that the "null island ghosting" is still happening when "Animate" button is originally pressed. This appears to be an issue of
|
Just did some quick testing and was able to isolate the "ghost issue" to public final void animateCamera (CameraUpdate update) {
// Order Matters! Otherwise Core GL will stomp on things
setCenterCoordinate(update.getTarget());
setZoomLevel(update.getZoom());
setTilt(new Double(update.getTilt()), 0L);
setBearing(update.getBearing());
} |
I tested @1ec5's public final void animateCamera (CameraUpdate update) {}
public final void animateCamera (CameraUpdate update, MapView.CancelableCallback callback) {}
public final void animateCamera (CameraUpdate update, int durationMs, MapView.CancelableCallback callback){} |
Ok, thanks to @friedbunny for straightening me out it turns out that the Compass is actually working as expected. It's job in life (as it is in the iOS SDK) is to always point North no matter what the Bearing is. In this case that means the the "red arrow" part always need to be pointing North. This is not as obvious as the iOS compass has a Ok, so the next part on this is to clean up the debug logs, investigate how to handle the callbacks, and test out use cases where not all CameraOptions are set (ie, bearing, tilt, and zoom) behave. Once these are done this iteration of the Camera API should be complete. |
|
Discussed options for implementing Callbacks for |
…s. Updating TestApp's CameraActivity to test for the three different options.
Added support for optional values of All in all, things are looking good here. @1ec5 is working on some improvements to the |
@bleege Cheering from the sidelines \o/ |
Per chat, @zugaldia kicked the tires this morning on the branch and is happy with things. The only tweaks that we'll make are adding Once these tweaks are made and tested that'll wrap up Iteration 0 on the Camera API and will then merge into /cc @twbell |
…() UIThread wrapping for Callback invoking. Restoring Callback Toasts in TestApp's CameraActivity.
Thanks to @jfirebaugh's help with git rebasing the Camera API is now merged into |
@bleege Is two finger drag gesture to tilt also available? |
@mb12 Yep. That's been in there since |
My Camera Animation is not working on API 23 and higher...but works fine on lower...Have this issue been solved? Please help!
here is how it's been called in the onMapReady() method
|
@KidusMT What SDK version are you using? Could you check if there are no exceptions printed in your |
@LukasPaczos For some reason which I am not sure why but it worked like this now
this is my SDK version defined in the build config
now its working on all API level I am targeting to work the app for. |
The next iteration of the map interaction API should be to add a Camera API. The Camera API will be modeled on the Google Maps Android API to maximize familiarity. Key classes will be:
/cc @zugaldia @incanus @twbell
The text was updated successfully, but these errors were encountered: