title: Understanding Fragment's setRetainInstance(boolean)
body: <p>Starting with the documentation:</p>
  <blockquote>
  <p>public void setRetainInstance (boolean retain)</p>
  <p>Control whether a fragment instance is retained across Activity re-creation (such as from a configuration change). This can only be used with fragments not in the back stack. If set, the fragment lifecycle will be slightly different when an activity is recreated:</p>
  <ul>
  <li>onDestroy() will not be called (but onDetach() still will be, because the fragment is being detached from its current activity).</li>
  <li>onCreate(Bundle) will not be called since the fragment is not being re-created.</li>
  <li>onAttach(Activity) and onActivityCreated(Bundle) will still be called.</li>
  </ul>
  </blockquote>
  <p>I have some questions:</p>
  <ul>
  <li><p>Does the fragment also retain its view, or will this be recreated on configuration change? What exactly does &quot;retained&quot; mean?</p>
  </li>
  <li><p>Will the fragment be destroyed when the user leaves the activity?</p>
  </li>
  <li><p>Why doesn't it work with fragments on the back stack?</p>
  </li>
  <li><p>Which are the use cases where it makes sense to use this method?</p>
  </li>
  </ul>