This repository has been archived by the owner on Jun 23, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 4.4k
Use of getSupportFragmentManager() instead of getFragmentManager() #271
Comments
getSupportFragmentManager() is relevant if you are supporting device below API 14 and not because we are using FragmentActivity. Anyway I don't see any usefulness of FragmentActivity at all. |
@elmargomez thank you for the clarification. |
@imageica you're very welcome. |
Hoyyyyaaaaaaaaaaaaa Finaly I Fixed that
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
To call the android.app.FragmentManager, shouldn't we be using,
getFragmentManager().beginTransaction().add(R.id.forecastListViewFragment,new
ForecastFragment()).commit();
Instead of,
getSupportFragmentManager().beginTransaction()
.add(R.id.container, new PlaceholderFragment())
.commit();
Since we are using Fragment and not FragmentActivity?
The text was updated successfully, but these errors were encountered: