getMapAsync for Android like in Google maps

[erf]

Would it be an idea to load the mapview async as in google maps:

   mapFragment = new SupportMapFragment();
        mapFragment.getMapAsync(this);

   FragmentManager fragmentManager = getSupportFragmentManager();
   FragmentTransaction fragmentTransaction = fragmentManager.beginTransaction();
   fragmentTransaction.replace(R.id.container, mapFragment);
   fragmentTransaction.commit();

In this way you could make the mapFragment static so you don't have to reinstanciate it each time you create the activity containing the map.

I have made an implementation of this.

[erf]

I created a pull request for this:
#2043

[erf]

The problem i described in #2018 is back after i load the mapview this way

[ljbade]

I don't really understand what this does.

It seems you are only changing the way the test app works?

/cc @bleege

[erf]

You probably would like to have MapView in a Fragment to reuse map functionality (like google do) and to add it programmatically you need to retrieve the MapView async from the MapFragment when it's added to the view or else it's null if you try to retrieve it just after you've created the MapFragment.

But.. This causes another problem, i describe in #2018 that when i tried to switch from the MapActivity to some other Activity (after moved the maped) and back the app crashes..

[tobrun]

@ljbade

I would like to add why Google exposes this async get method:

This would crash because the MapFragment is not created/attached yet, for this reason an async callback was introduced.

cc @bleege

[tobrun]

Also here is an example how getMap can work, I used to implement GoogleMaps in this fashion before the async method was introduced and getMap was deprecated:

[ljbade]

@tobrun Interesting! Perhaps we should put this on 2.2.0 milestone as part of the refactor.

[tobrun]

This will be implemented with #3145

[tobrun]

This has landed with #3145. Closing