Hi, I have an issue with fragment lifecycle and the fragment back stack. I'm pushing two fragments A and B onto the stack, both display a view of the underlying data model. Fragment B will alter the model, and will then be popped from the stack, causing A to reappear.
What I expected is that at this point, fragment A will receive an onResume lifecycle callback, similar to an activity that is being resumed after another one disappears. However, this does not seem to be the case. What I'm trying to achieve is to refresh controls in fragment A pertinent to parts of the model that fragment B altered, like for instance a ListAdapter. As a workaround, I can create a callback interface for fragment B, which would allow the hosting activity to manually call some kind of "refresh" method on my fragment A, however I don't much like it, since I have to find the fragment by ID and typecast the fragment to the fragment A class. Also introducing an extra method for something that should IMHO be covered by the lifecycle is rather unappealing. Am I overlooking something here? Would love some input from Dianne or Romain, if possible. :-) Regards, Alex -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
