You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You've documented a 'wierdness' with v4 compat for onResume/onPostResume. It's worth saying that onResume() should be used for normal Activity's and onResumeFragments() when using the v4 compat library. This is only required when the application is waiting for the initial FragmentTransaction's to be completed by the FragmentManager. For instance the application wants to access a Fragment that was inflated during onCreate(). The best place for this is onResumeFragments().
Yeah, that's a good call. I was having trouble figuring out how to incorporate the differences in v4 vs. standard, but your suggestion of simply stating to use onResumeFragments() instead of onResume() for v4 is a good one.
I think this should still be documented but it looks like they are now fixing several issues. https://youtu.be/k3IT-IJ0J98?t=14m43s (What the Fragment talk from Google I/O 2016)
You've documented a 'wierdness' with v4 compat for onResume/onPostResume. It's worth saying that onResume() should be used for normal Activity's and onResumeFragments() when using the v4 compat library. This is only required when the application is waiting for the initial FragmentTransaction's to be completed by the FragmentManager. For instance the application wants to access a Fragment that was inflated during onCreate(). The best place for this is onResumeFragments().
See: http://developer.android.com/reference/android/support/v4/app/FragmentActivity.html#onResumeFragments%28%29
The text was updated successfully, but these errors were encountered: