fragmenttransaction

At present I have got a "RELATIVE_LAYOUT" container which I am using for adding my fragment. I am using OnClickListener on a button to load the fragment XML layout into the RelativeLayout container. What I want to achieve is that when I press the button once, the fragment should load...and when I press it again the fragment should be removed. I've already tried using integer to identify if fragment is loaded, but failed. Any help Appreciated... CODE: public class MainActivity extends Activity { Button B1,B2; int boolb1=0, boolb2=0; @Override protected void onCreate(Bundle savedInstanceState) {

I was studying Fragments and got little confused on differentiating FragmentTransaction.replace(id, fragment, tag) and FragmentTransaction.addToBackStack(tag) calls. Lets say that my current fragment is FragmentA and then I loaded FragmentB . I want that in future, when I need to load FragmentA , I don't have to reload it. Just load the old one in old state. I used the following code segment: public void loadFragment(Fragment fragmentB, String tag) { FragmentManager fm = getSupportFragmentManager(); View fragmentContainer = findViewById(R.id.fragment_container); FragmentTransaction ft = fm

I have an activity with two fragments, one to display a list and one to show the details of the clicked item. When starting the app the detail part is something static, once I click an item it should get replaced. The problem is that the old fragment is not being replaced, so both views are on top of each other. My activity layout is: <?xml version="1.0" encoding="utf-8"?> <fragment android:id="@+id/listFragment" android:layout_width="0dp" android:layout_height="match_parent" android:layout_weight="1" class="com.fragments.FragmentOrderList" > </fragment> <fragment android:id="@+id

I am developing an app that uses fragments, last week my test device took lolipop update. When I test my app on a lolipop device, I saw that Fragment Transaction's replace method didn't work properly. It work with confusingly in Lolipop version although everything fine on Kitkat version. In order to explain my situation, I've added some images. --First Screen----------------------------KitKat-------------------------------------Lollipop------------- As you can see, when i use kitkat , everything fine but as soon as i use lolipop fragment transaction replace is working confusingly. Here is my

My app has several fragments and activities. Over the course of the main parent activity's lifecycle, the app presents information/options to the user in other activities. The documentation for Fragments has the following stipulation for commit(): Caution: You can commit a transaction using commit() only prior to the activity saving its state (when the user leaves the activity). If you attempt to commit after that point, an exception will be thrown. This is because the state after the commit can be lost if the activity needs to be restored. For situations in which its okay that you lose the

I have created several fragments and I add the first fragment the following way: mainFragment = (MainFragment) MainFragment.create(); getSupportFragmentManager().beginTransaction() .setCustomAnimations(R.anim.slide_in_right, R.anim.slide_out_left, R.anim.slide_in_left, R.anim.slide_out_right) .add(R.id.content, mainFragment, MAIN_FRAGMENT_TAG) .commit(); The second fragment is added this way: getSupportFragmentManager().beginTransaction().setCustomAnimations(R.anim.slide_in_right, R.anim.slide_out_left, R.anim.slide_in_left, R.anim.slide_out_right) //.hide(mainFragment) .add(R.id.content