On Sun, Aug 29, 2010 at 6:24 PM, William Ferguson <william.ferguson.au@ gmail.com> wrote:
> Not real sure about this, just putting it out there .. > But is is possible that Activity2 is started in a separate Task to > Activity1? > I can find any doco confirming or denying, but perhaps separate Tasks > run in separate JVMs, hence the potential for non-initialization. > What's the taskAffinity? > All activities in the same process have their callbacks called on the same (main) thread of the process. All activities in a .apk will run in the same process, by default, unless you explicitly override their behavior with android:process. If you do that, those activities will run in the process indicated, which has its own VM, statics, etc., completely isolated from other processes. -- Dianne Hackborn Android framework engineer hack...@android.com Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. -- 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
