On Fri, Mar 12, 2010 at 12:19 PM, Jeffrey <[email protected]> wrote:
> What I have done with success in some of my apps is making several > parent views that hold each layout within a table layout, and use the > menu buttons to change the visibility of the parent view containing > the info you want them to see. > Yeah, but in the OP's case there is an on going Service that directly relates to the child activity. If you did one activity with hidden views and closed the app, you would still have to store the text / image information related to that service *somewhere* to get it back when you reopened the activity. Assuming the service has an on-going notification in the status bar (like the default music player), one would expect that clicking that would take you back to the activity with the relevant info. In this case, it would make sense to let the service save the relevant data to pass on to the activity when it needs to. In this case I think binding to the Service when your associate activity is created makes the most sense. Again, haven't done anything like this myself, so I could be way off here. HTH. ------------------------------------------------------------------------------------------------- TreKing - Chicago transit tracking app for Android-powered devices http://sites.google.com/site/rezmobileapps/treking -- 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
