Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update required for onResume() / onResumeFragments() #8

Open
slightfoot opened this issue Jul 11, 2014 · 4 comments
Open

Update required for onResume() / onResumeFragments() #8

slightfoot opened this issue Jul 11, 2014 · 4 comments

Comments

@slightfoot
Copy link

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

@xxv
Copy link
Owner

xxv commented Aug 18, 2014

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.

@jeffdav
Copy link

jeffdav commented Apr 26, 2016

+1

1 similar comment
@ptran-gpfw
Copy link

+1

@slightfoot
Copy link
Author

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)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants