RecyclerViewAdapter | Multiple type RecyclerView Adapter , combine | RecyclerView library

You're attaching a ChildEventListener on /users. This means that your onChildAdded is called with the direct child nodes of users, which is m50... in your screenshot. Then you read the value of the ricette child under there, which leads to all the 9999, dfsdfdf, etc nodes under there.

My guess it that you're trying to read one or all child nodes under ricette, for which you'll need to loop over the child nodes of the snapshot with:

Documentation:

Volley always delivers parsed responses on the main thread. Running on the main thread is convenient for populating UI controls with received data, as you can freely modify UI controls directly from your response handler

So onResponse() callback is triggered in the Main thread, and so as callBack.processFinished() call.

So, you can safely build-up the RecyclerView when the processFinished() is triggered.

You could have a look at documentation for more info.

Also make sure not to have a heavy work on this callback as it runs on main thread.

I want to store that if I click on 5th Item, then on app restart it should change display of only 5th item, not for every item.

Your Problem

A ViewHolder represents one item in the RecyclerView. When you initialize your ViewHolder you apply the preference 7 times to the same button.

The network request etc runs on a background thread, but the callback doesn't.

However I think your misunderstanding here comes from how callbacks work. When you pass in an EventListener here, you're passing in a class (in this case, an anonymous class) which overrides the onEvent method. There's nothing to "skip over" as you mentioned.

Let's consider an example. Say I defined an interface Callback:

You are almost there. Instead of checking the adapterPosition, and starting an Activity, you want to pass your data to the ViewHolder, and then to the Activity. You can use onBindViewHo\lder() for the first, and [Intents][1] for the second part.

I would not use TableLayout and TableRow as TableLayout extra logic to resize any child that is a TableRow BUT as you only have one TableRow as a child of the TableLayout that logic is redundant and is less efficient.

The TableRow's that are inside the RecyclerView are the children of the RecyclerView not children of the TableLayout and as the Docs says

If a TableRow's parent is not a TableLayout, the TableRow will behave as an horizontal LinearLayout

And thus won't do any of their normal resizing of the table columns

So in practice you have actually got a structure like:-

Since your listId is String ,the list gets sorted lexographically. Instead you could first convert the String to an Integer and then sort it. Below is the illustration.

Ok, it's normal you have this message because in your code, you' ll do this :

There are two ways

(1) While inflating the data you can filter these unwanted values (2) Create a temporary list and add only required values from the main list. sample code: