Retrieve map state while switching between fragments about android-samples HOT 9 CLOSED

thanks 💯

from android-samples.

Well it's maybe too late and the problem is solved, but for others with that problem the solution from me can help.

I had the same problem with a laggy map when switching between fragments from navigation in one activity. I think it's a specific way to implement such a structure but anyway.

So the solution for the map to just save the map in its rendered status and don't mess up recreating it when getting back to the fragment, is to check if its not null.

so I use the MapFragment, but you could change your code to fit into it.

In your MainFragment.java you have to check it your actual Map is not null

In the onCreateView Method from Fragment:

if (mMap == null) {
fusedLocationProviderClient = getFusedLocationProviderClient(getActivity());
SupportMapFragment supportMapFragment = (SupportMapFragment) getChildFragmentManager().findFragmentById(R.id.mapView);
supportMapFragment.getMapAsync(this);
}

So the getMapAsync Task is only called when there is no initialized Map and while there was one he is using it.

from android-samples.

there is no answers or updates or any workaround to this issue ?

from android-samples.

it is old, I guess the only way is that you save the state of the map before any change then reload it again from the stack

cheers

from android-samples.

didn't get your ans. please elaborate little bit more @AryaRDI .
thanks !

from android-samples.

This issue has been automatically marked as stale because it has not had recent activity. Please comment here if it is still valid so that we can reprioritize. Thank you!

from android-samples.

i have same trouble

from android-samples.

In the future, for help with specific situations you'll get the fastest response on StackOverflow (tag google-maps-android-api-2).

For this question, you may want to check out the demos for RetainMap and SaveState.

from android-samples.

You could try to "Add" fragments instead of replacing them.
It will not destroy the previous fragment view, so it won't be necessary to reload the data.

Example:

        val fragment = TheFragment()
        val ft = requireActivity().supportFragmentManager.beginTransaction()

        ft.add(R.id.fragment_container, fragment)
        ft.commit()

from android-samples.