Further Discussion of AdapterView and Adapter Request Issue # 1944

by Dianne Hackborn » Tue, 10 Feb 2009 18:17:08 GMT


Sponsored Links
 Dialog is a good point, but the lifecycle would need to be managed by the
dialog, not by ListView.  At the ListView level there just isn't enough
information to manage it correctly -- that is, the management that would be
added for Dialog would be fairly different that what we currently have for
Activity.






-- 
Dianne Hackborn
Android framework engineer
hack...@android.com

Note: please don't send private questions to me, as I don't have time to
provide private support.  All such questions should be posted on public
forums, where I and others can see and answer them.

--~--~---------~--~----~------------~-------~--~----~



Further Discussion of AdapterView and Adapter Request Issue # 1944

by Jonathan Herriott » Tue, 10 Feb 2009 18:41:35 GMT


 When you say there isn't enough information, I'm assuming you mean
that the views don't know when they are being released from memory.
In that case, the two options would be to have views death-aware or to
have the Dialog manage its lifecycle.  I'm sure the choice really boil
down to performance/memory usage, and in that case, the Dialog
managing its lifecycle is probably the best option.  If you agree,
I'll file a new bug on the Dialog.




--~--~---------~--~----~------------~-------~--~----~


Sponsored Links


Further Discussion of AdapterView and Adapter Request Issue # 1944

by Dianne Hackborn » Tue, 10 Feb 2009 21:22:39 GMT


 eah I think this would belong in Dialog.

On Tue, Feb 10, 2009 at 10:34 AM, Jonathan Herriott <herri...@gmail.com>wrote:



--
Dianne Hackborn
Android framework engineer
hack...@android.com

Note: please don't send private questions to me, as I don't have time to
provide private support. All such questions should be posted on public
forums, where I and others can see and answer them.

--~--~---------~--~----~------------~-------~--~----~