Okay, I'll have to opt for the stop/start approach each time you switch from Activity to Activity - its not a very elegant solution though.
Im suprised theres not a "whole application has lost focus".onPause(). On Jan 17, 3:27 pm, Mark Murphy <mmur...@commonsware.com> wrote: > mscwd01 wrote: > > Isn't onPause() called when one Activity calls another too? > > Sure. > > > I want to know when an entire Activity has lost focus, > > What is "an entire Activity"? > > > if I use onPause > > () in an Activity which calls another, when the other Activity has > > started the initiating Activity's onPause() method is called. > > Correct. Suspend network activity on every onPause(); re-enable network > processing on every onResume(). Then, if any activity is active, network > processing is in operation; if all are paused, network processing is > stopped. > > If by "an entire Activity" you really mean "an entire application", so > long as all the components are in the same process, and so long as you > use loose coupling so garbage collection isn't impeded, you can > communicate among collaborating activities however you wish. > > -- > Mark Murphy (a Commons Guy)http://commonsware.com > _The Busy Coder's Guide to Android Development_ Version 2.0 Available! --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
