If you have a world simulation with lots of entities an what not it adds
up. I just did some tests and onSaveInstanceState() always gets called
when my activity is put into the background. This is an unnecessary
burden to put on the app developer and will lead to many game developers
to just killing their activity and forcing the user to pay for the
reload. The framework should have been written for the common case and
not the extreme. Who's idea was it anyway to encourage the user to
leave a trail of open apps behind them!
Leigh
On 6/7/2010 9:36 PM, Frank Weiss wrote:
I wonder what you mean by a fair amount of serialization. It would
seem to me a kilobyte or so would suffice for most mobile
applications. If it's much, much more than that, I think someone
suggested using a caching strategy instead. I would suppose that means
setting aside a few megs on the SD Card and storing your state there,
pulling it into main memory only when it's needed.
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
--
Leigh McRae
www.lonedwarfgames.com
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
