How would you want to make it more transparant? If you want to kill activities when they are in the background and restore them when the user wants to see it again you have to save the state of the objects. Saving the state of objects is only possible if you marshal the object. If you only have a pointer to an object 'owned' by another activity you can't save the object to disk.
- If you save the reference the reference may be invalid by the time the activity returns. - If you save the object the other activity still needs to be able to access that object So there is really no other way then to duplicate the object (using parceble) when you want to use the same data in multiple activies, or you have to use a seperate shared data source such as a content provider, or you have to create some other strategy where you make sure the data stays consistent. On Mar 26, 6:08 pm, Raja Nagendra Kumar <[EMAIL PROTECTED]> wrote: > Hackbod, > > I clearly understand this swapping approach to release the resources > and memory. But question is why the framework can't handle this > transperently i.e transperently storing the object status of > background process it is killing and getting it back with out > programmer need to take care of such situations.. Pl. look at as > general comments and not only perticular to andorid alone. Trying to > see some thoughts based on my expertise with spring,where interfaces > does not matter for it do interception etc.. > > Regards, > Nagendra --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
