Lines Matching refs:commit
169 should commit any changes that should be persisted beyond the current user session (because
344 fragmentTransaction.commit();
352 call {@link android.app.FragmentTransaction#commit} for the changes to take effect.</p>
411 commit to the activity is called a transaction and you can perform one using APIs in {@link
428 to the activity, you must call {@link android.app.FragmentTransaction#commit()}.</p>
432 android.app.FragmentTransaction#commit()}, however, you might want to call {@link
451 transaction.commit();
464 before you call {@link android.app.FragmentTransaction#commit commit()} are added to the
470 <li>You must call {@link android.app.FragmentTransaction#commit()} last</li>
484 you commit.</p>
486 <p>Calling {@link android.app.FragmentTransaction#commit()} does not perform the transaction
490 transactions submitted by {@link android.app.FragmentTransaction#commit()}. Doing so is
493 <p class="caution"><strong>Caution:</strong> You can commit a transaction using {@link
494 android.app.FragmentTransaction#commit commit()} only prior to the activity <a
496 state</a> (when the user leaves the activity). If you attempt to commit after that point, an
497 exception will be thrown. This is because the state after the commit can be lost if the activity
498 needs to be restored. For situations in which its okay that you lose the commit, use {@link