java - Previously detached fragment stays visible behind the current, after tab changed (using support library) -

-

here tablistener:

    public class tablistener<t extends fragment> implements android.support.v7.app.actionbar.tablistener {      private fragment mfragment;     private final activity mactivity;     private final string mtag;     private final class<t> mclass;      public tablistener(activity activity, string tag, class<t> cl) {         mactivity = activity;         mtag = tag;         mclass = cl;     }      @override     public void ontabreselected(tab arg0, fragmenttransaction arg1) {         // todo auto-generated method stub               }      @override     public void ontabselected(tab tab, fragmenttransaction ft) {          mfragment = ((fragmentactivity) mactivity).getsupportfragmentmanager().findfragmentbytag(mtag);   // add          if (mfragment == null){              mfragment = android.support.v4.app.fragment.instantiate(mactivity, mclass.getname());              ft.add(android.r.id.content,mfragment,mtag);         } else {             ft.attach(mfragment);         }                  }      @override     public void ontabunselected(tab tab, fragmenttransaction ft) {         mfragment = ((fragmentactivity) mactivity).getsupportfragmentmanager().findfragmentbytag(mtag);   // add         if (mfragment != null) {             //toast.maketext(mactivity, "detached", toast.length_short).show();             ft.detach(mfragment);         }     }  }

and part of activity:

public class roadmapactivity extends actionbaractivity {  listview generalroadmaplist; listview mainroadmaplist; android.support.v7.app.actionbar actionbar;  @override protected void oncreate(bundle savedinstancestate) {     super.oncreate(savedinstancestate);     setcontentview(r.layout.activity_roadmap);      actionbar = getsupportactionbar();             actionbar.setdisplayshowtitleenabled(false);     actionbar.setdisplayuselogoenabled(true);            actionbar.setnavigationmode(actionbar.navigation_mode_tabs);      tab generaltab = actionbar.newtab()             .settext("general")             .settablistener(new tablistener<generallistfragment>(this, "general", generallistfragment.class));     actionbar.addtab(generaltab);      tab mytab = actionbar.newtab()                         .settext("my")                         .settablistener(new tablistener<mylistfragment>(this, "my", mylistfragment.class));     actionbar.addtab(mytab); }

i tried change viewgroup android.r.id.content custom view group activity's layout, next thing happens:

i have 2 tabs, , b. after starting activity active tab , content fragment a. if switching b, tab b gets active, content still fragment a. change tab a, , content fragment b. change tab b, content fragment a... without showing other fragment behind, whit changed content.

i've tried everithing found on google , here, without sucess. have idea?

you instantiating fragments wrong. have @ revised method.

@override public void ontabselected(tab tab, fragmenttransaction ft) {     fragment mfragment;    switch(tab.getposition(){       case 0:        /* create fragment in here based on tab, mfragment = new examplefrag */         break;      case 1:        /* create fragment in here based on tab, mfragment = new examplefrag */         break;    }     ft.replace(android.r.id.content, mfragment); }  @override public void ontabunselected(tab tab, fragmenttransaction ft) {    // dont need anything. }

much more simple.

worth noting shouldn't use android.r.id.content actionbaractivity prior android 3.0 support action bar gets added android.r.id.content , replacing fragment it, remove actionbar. (nasty know.)


Comments

Post a Comment

Popular posts from this blog

c# - How Configure Devart dotConnect for SQLite Code First? -

-
can configure following sample code ? when run following code, error : no entity framework provider found ado.net provider invariant name 'devart.data.sqlite' setting in machine.config <system.data> <dbproviderfactories> <add name="dotconnect sqlite" invariant="devart.data.sqlite" description="devart dotconnect sqlite" type="devart.data.sqlite.sqliteproviderfactory, devart.data.sqlite, version=4.6.287.0, culture=neutral, publickeytoken=09af7300eec23701" /> </dbproviderfactories> </system.data> after add below block code in app.config <?xml version="1.0"?> <configuration>   <configsections> <!-- more information on entity framework configuration, visit http://go.microsoft.com/fwlink/?linkid=237468 --> <section name="entityframework" type="system.data.entity.internal.configfile.entityframeworksection, entit...
Read more

c++ - Clear the memory after returning a vector in a function -

-
i have function processes , stores lot of data in , returns results vector of class. amount of data stored in function tremendous , want clear storage memory of function after finished job. necessary (does function automatically clear memory) or should clear memory function? update: vector<customers> process(char* const *filename, vector<int> id) { vector<customers> list_of_customers; (perform actions) return list_of_customers; } variables defined locally within function automatically released @ end of function scope. destructors objects called, should free memory allocated objects (if objects coded correctly). example of such object std::vector . anything you've allocated new must have corresponding delete release storage. try avoid doing own allocation , use raii instead, i.e. containers or smart pointers.
Read more

erlang - Saving a digraph to mnesia is hindered because of its side-effects -

-
updated the digraph library in erlang implements data type side-effectful. each operation on data type saves new state in ets table -- instead of returning altered version of itself, more common in functional languages. the problem usage perspective, impedes effort store or pass around state in convenient way requiring me first "collect" state before can start juggle around. the closest solution have seen far serializer/deserializer , these have drawback tied current structure of digraphs instead of operating on abstract type -- prevents future proof solution. update pascal pointed out serializer utilizes interface of digraph, , hence eliminates drawback mentioned above. better, albeit still inconvenient, see no better alternative. what recommendation on how store digraphs? should go different data type altogether? thanks. i not sure understand concern. fact digraph stored in ets transparent in user interface, might want chnge either exchange digr...
Read more