Our designers like the idea of integrating the action bar with the back stack, but we haven't found a realistic way to do that. We have been jumping through hoops with work arounds like adding empty transactions to the back stack (with no removes or adds) and keeping track of where we are and restoring the tabs and fragments to the state at that point. Seems like we have departed quite a ways from the supported behavior of the fragment back stack.
A related thing is we don't want the activity to exit when the back button is pressed if there have been a series of action bar tab selections that we want to traverse back through. Does anyone have any thoughts about how to organize the UI to get a good user experience with the action bar and fragment back stack that "works" with the Honeycomb use case model? -- 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
