-
Notifications
You must be signed in to change notification settings - Fork 493
locationEngine needed? #248
Comments
cc: @tobrun |
That's correct, the Maps SDK takes care of setting up a default |
I'd argue setting up a custom locationEngine instead of using LocationSource could make for a good example. I have found that some users get confused with the ordering in which the APIs need to be called. |
👍 Let's ticket that separately and use the API introduced by mapbox/mapbox-gl-native#8710 (now merged). Meanwhile, let's remove the redundant initialization from this example. |
@cammace advised that I open this ticket.
The question is what to do with the following two lines.
Previously, Cameron said: "If we are simply displaying the user location icon on the map through the SDK, I don't think there's a reason to create a locationEngine object and activate it. This should be take care of by the Maps sdk"
Because those two lines were included in the demo app, they were also used in the user location example page as well.
If the lines are removed, then it affects camera movement and LocationEngineListener stuff in
enableLocation()
Here's the code for the user location activity in the demo app:
The text was updated successfully, but these errors were encountered: