It's possible: In your app's manifest-file, you can set the *android:process* attribute of an <activity>. If this is set different than your 'default' process of your application, it'll run in a different process. Note that you should hardly ever use this, though. I use it in my app, because one of the activities is an image editor, while other activities in my app are an image-picker, settings, etc.. The image-editor activity needs every bit of memory it can possibly get: I give it a separate process of its own.
-- 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
