If you want to keep them across instances, you need to save and restore them
just like in an activity.  My blog post shows an example of this, retaining
the mCurCheckPosition variable across instances.

On Thu, Feb 17, 2011 at 1:09 PM, Satya Komatineni <
[email protected]> wrote:

> A fragment can be instantiated using its default constructor by the
> base framework.
>
> The initialization arguments are passed as  a bundle that can be
> restored and reset.
>
> How about local variables for managing state of that fragment?
>
> Does one need to use the bundle to insert/remove these local variables?
>
> Or does one need to reset local variables based on lifecycle methods
> and valid only for the current life of the fragment?
>
> Appreciate your coments and help
> Satya
>
> --
> 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
>



-- 
Dianne Hackborn
Android framework engineer
[email protected]

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

-- 
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

Reply via email to