Lines Matching full:perform
70 manipulate each fragment independently, such as add or remove them. When you perform such a
313 capture the fragment to perform
403 to open a {@link android.app.FragmentTransaction}, which allows you to perform transactions, such as
410 and perform other actions with them, in response to user interaction. Each set of changes that you
411 commit to the activity is called a transaction and you can perform one using APIs in {@link
424 <p>Each transaction is a set of changes that you want to perform at the same time. You can set
425 up all the changes you want to perform for a given transaction using methods such as {@link
476 addToBackStack()} when you perform a transaction that removes a fragment, then that fragment is
486 <p>Calling {@link android.app.FragmentTransaction#commit()} does not perform the transaction
511 android.app.Fragment#getActivity()} and easily perform tasks such as find a view in the
720 activity in order to perform actions such as build and destroy the fragment's UI. These additional
