android - RecyclerView Adapter gives error "The hierarchy of the type RecycleAdapter is inconsistent" -

-

i trying add new recyclerview project inside fragement. following video tutorial on link1 . when try create adapter recyclerview, start getting error. using eclipse juno. cant figure out problem. please help

my code:

public class recycleadapter extends recyclerview.adapter<recycleadapter.myviewholder> {  private layoutinflater inflator; list <item> data = collections.empty_list;  public recycleadapter(context context, list<item> data){     inflator = layoutinflater.from(context); }  @override public int getitemcount() {     // todo auto-generated method stub     return data.size(); }   @override public myviewholder oncreateviewholder(viewgroup parent, int arg1) {     view view = inflator.inflate(r.layout.row_staggered_new, parent, false);     myviewholder holder = myviewholder(view);     return holder; }  @override public void onbindviewholder(myviewholder holder, int position) {     item current = data.get(position);     holder.text.settext(current.title);     holder.image.setimageresource(current.image);  }  public static class myviewholder extends recyclerview.viewholder{      public imageview image;     public textview text;      public myviewholder(view itemview) {         super(itemview);         image = (imageview) itemview.findviewbyid(r.id.imageview1);         text = (textview) itemview.findviewbyid(r.id.textview1);     } } }

both myviewholder , recycleadapter giving error "the hierarchy of type recycleadapter inconsistent". in extends part of recycleadapter, shows error "bound mismatch: type recycleadapter.myviewholder not valid substitute bounded parameter <vh extends recyclerview.viewholder> of type recyclerview.adapter<vh>".

any pointers?

i found problem. issue was using older version , v4 support library not contain class android.support.v4.view.scrollingview class. replaced old v4 library new version , error gone!


Comments

Post a Comment

Popular posts from this blog

java - Custom OutputStreamAppender not run: LOGBACK: No context given for <MYAPPENDER> -

-
i wish write custom appender on basis of outputstreamappender . wrote following class package tests; import java.io.ioexception; import java.io.outputstream; import ch.qos.logback.core.outputstreamappender; public class myappender<e> extends outputstreamappender<e> { public myappender() { system.out.println("myappender created"); setoutputstream(new outputstream() { @override public void write(int b) throws ioexception { throw new unsupportedoperationexception(); } }); } } then wrote following runner: package tests; import org.slf4j.loggerfactory; import ch.qos.logback.classic.logger; public class runner { private static final logger log = (logger) loggerfactory.getlogger(runner.class); public static void main(string[] args) { //log.addappender(new myappender<iloggingevent>()); log.info("hello world"); } } finall...
Read more

java - UML - How would you draw a try catch in a sequence diagram? -

-
Image
is there standard way of drawing try catch sequence diagrams? i've made attempt based on this feel end result doesn't feel right. code diagram based around: public static void save () { try { filehandle filehandle = gdx.files.external(file); filehandle.writestring(boolean.tostring(constantshandler.soundenabled)+"\n", false); (int = 0; < 5; i++) { filehandle.writestring(integer.tostring(constantshandler.highscores[i])+"\n", true); } } catch (throwable e) { } } my attempt note: know still need add loop. that's ok. fragments meant show conditional control flow in sequence diagram. superstructures puts limitations on use of fragments (see pp. 467 of ss2.1.1). should use critical region try part above. , option catch . however, keep telling can take quite freedom in using uml. it's language , such changes in life time. long reader ge...
Read more

c++ - No viable overloaded operator for references a map -

-
i trying use map can make tag names reference number. when try , use it, in code error (6 in total every time reference map): src/main.cpp:25:45: error: no viable overloaded operator[] type 'std::map<std::string, std::string>' const char* idcs = node.child_value(tagmap[3]); this code: #include "pugi/pugixml.hpp" #include <iostream> #include <string> #include <map> int main() { pugi::xml_document doca, docb; std::map<std::string, pugi::xml_node> mapa, mapb; std::map<std::string, std::string> tagmap {{"1", "data"}, {"2", "entry"}, {"3", "id"}, {"4", "content"}}; if (!doca.load_file("a.xml") || !docb.load_file("b.xml")) { std::cout << "can't find input files"; return 1; } (auto& node: doca.child(tagmap[1]).children(tagmap[2])) { co...
Read more