How I did such applications is that on ,say a button click, I setContentView to another (supposedly) activity, and did its initializations, overrode the onBackPressed method to reflect changes when back button was pressed. But I am sure my way is one of the bad ways to go about it. It makes the code difficult to read,maintain and quiet messy. So may be that is a workaround, it is not the best approach.
On Tue, May 29, 2012 at 1:03 PM, TreKing <treking...@gmail.com> wrote: > On Tue, May 29, 2012 at 1:16 AM, LordMaKo <juanman...@gmail.com> wrote: > >> is it a better approach to use >> fragments<http://developer.android.com/guide/topics/fundamentals/fragments.html> >> as >> aneal [SO user] suggest? >> > Yes. From what I've gathered in this group, ActivityGroup was a hack and > should not be used. > > > ------------------------------------------------------------------------------------------------- > TreKing <http://sites.google.com/site/rezmobileapps/treking> - Chicago > transit tracking app for Android-powered devices > > > -- > You received this message because you are subscribed to the Google > Groups "Android Developers" group. > To post to this group, send email to android-developers@googlegroups.com > To unsubscribe from this group, send email to > android-developers+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en > -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
