On Mar 24, 2:26 pm, Raja Nagendra Kumar <[EMAIL PROTECTED]> wrote: > I did try this approach by using setContentView.. however it seems to > have some restrictions on view beeing changable by only the thread > which created the activity or so.. hence I had no choice other than > going with intent approach. I am guessing I may need to use method > runinuithread() or use handler and Looper etc.
It is true that the UI for a particular window can only be accessed by the thread that owns that window, but I don't think there is anything about separating things into activities or not that has anything to do with this: the system calls and runs all activities in the same (main) thread of the process. It does not make a new thread for each activity. So whether you switch views in one activity, or start multiple activities (in the same process), at the threading level it is exactly the same. > if statics are reset, what is the fate of object variable, which does > not implement serialisable etc. The process is killed. Everything in it goes away, except whatever you put into the icicles in onFreeze() and what was given to the system to start the activities in that process. When the process comes back, it starts over from the very beginning, and the system launches activities into it from a completely fresh state: the only things that are retained are the Intent and icicle that will be given to onCreate(). --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] Announcing the new M5 SDK! http://android-developers.blogspot.com/2008/02/android-sdk-m5-rc14-now-available.html For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
