I saw this on a post from last January ~ monkey wrench in the works
represented by Android's handling of image data outside of the Java
heap ~ seems simple enough to do aggressive nulling but it does not
sound like Android is doing the right thing here
given that the docs state Activity Lifecycle Android will work on the
idea that onPause() will be called in anything other than "brutal-
dump" then one can write to Bundle and get it back when focus returns
to the application
thus we could just check objects for null and if Object != null
then .... would the value have been retained?....
seems rather simple - what gives?..
Object value;
MyClass(){ if (value == null) { value=new Object(); } }
then if user wants to flip the phone around maybe we ^do^ need a new
Object()
maybe not
if phone is filpped 20 times user may have to wait on gc but all of
that is in the vendor's shop and would have to be hard-wired to work
with the "whole thing" ~ trying to code away monkey wrench when one
does not know where it is leads to knarled ....
suggestions on how to design ?..
--
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
