My architecture is MVVM. For implementing paging I used paging library from architecture component.
I need paging for outer recycler view and inner recycler view. For outer recycler view I successfully implemented it, but for inner recycler view I don’t know how to implement.
I implemented paging like in this article for outer recycler view
https://proandroiddev.com/8-steps-to-implement-paging-library-in-android-d02500f7fffe
UPDATE
I implemetened my inner recycler view like this example and it works, but I think it's not preferable solution
how to use paging when recyclerview item have another recyclerview
Just add ViewPager inside your ViewHolder item view, and do all ViewPager logic inside onBindViewHolder()
Related
How do I build a screen where I have a vertical recyclerView and its items are horizontal recyclerView but using paging 3?
I don't know how to pass the pagingData into the childAdapter
How can I implement this kind of UI, where we have two recyclerViews. One scrolls horizontally and the second one vertically. when the second one scrolls first one also scrolls top together.
I tried to implement using NestedScrollView, but I had to make second recyclerView height wrap content which causes recyclerView not recycle.
The second way that I tried was having one recyclerView. And adding horizontal recyclerview as a header. The problem was to save header recyclerview scroll state when navigation. And there had been crashes when loading next page (paging 3) in header recyclerView.
The question is: Is there any optimal solution for this kind of ui?
In cases, Like this, you don't have to use 2 RecyclerView and you also have to avoid using RecyclerView insideScrollView. instead of this you have to use one vertical RecyclerView with multitype view Adapter.
in this way, you are going to have 2 different ViewHolder one of them is a horizontal recyclerView (your top item) and the other one is your other items.
for learning multitype adapter you can see this:
How to create RecyclerView with multiple view types
and for a horizontal recyclerView inside a vertical RecyclerView you can see this :
https://medium.com/#ashishkudale/android-list-inside-list-using-recyclerview-73cff2c4ea95
you have to combine these 2.
I could not understand the meaning of "header" where you said "adding horizontal recyclerview as a header" but if you did what I told and the problem is the state of inner Horizontal recyclerView, I think probably you are calling setAdapter method of horizontal RecyclerView in OnBind() method of your vertical recycler view, it is a common mistake that I have seen in many tutorials.
if you have done this mistake , try to call setAdapter of your inner recyclerView in the constructor of its viewHolder and just update the list using yourHorizontalAdapter.notifyDataSetChanged() in onBind() method of VerticalRecylerView,
and if its not the case and your recyclerView is completely destroying see this link :How to save RecyclerView's scroll position using RecyclerView.State?
I'm trying to design a row list using RecyclerView like Android TV ↳ android.support.v17.leanback.widget.ListRow. I'm able to design list with title but not row list. Can anyone help me?
Please Follow this Link for
Recycer view like play store
Use Two RecyclerView Outer Recycler is vertical and Second horizontal recycler is item of first recycler View
All you need is to call mInnerRecycler.setNestedScrollingEnabled(false); on your inner RecyclerViews and use Horizontal scrollview as root of mInnerRecyclerView
Explanation:
RecyclerView has support for nested scrolling introduced in API 21 through implementing the NestedScrollingChild interface. This is a valuable feature when you have a scrolling view inside another one that scrolls in the same direction and you want to scroll the inner View only when focused.
In any case, RecyclerView by default calls RecyclerView.setNestedScrollingEnabled(true); on itself when initializing. Now, back to the problem, since both of your RecyclerViews are within the same ViewPager that has the AppBarBehavior, the CoordinateLayout has to decide which scroll to respond to when you scroll from your inner RecyclerView; when your inner RecyclerView's nested scrolling is enabled, it gets the scrolling focus and the CoordinateLayout will choose to respond to its scrolling over the outer RecyclerView's scrolling. The thing is that, since your inner RecyclerViews don't scroll vertically, there is no vertical scroll change (from the CoordinateLayout's point of view), and if there is no change, the AppBarLayout doesn't change either.
In your case, because your inner RecyclerViews are scrolling in a different direction, you can disable it, thus causing the CoordinateLayout to disregard its scrolling and respond to the outer RecyclerView's scrolling.
Notice:
The xml attribute android:nestedScrollingEnabled="boolean" is not intended for use with the RecyclerView, and an attempt to use android:nestedScrollingEnabled="false" will result in a java.lang.NullPointerException so, at least for now, you will have to do it in code.
RecyclerView can check View Type for return header or item. And use layout manager for manage how to item scrolling direction.
RecyclerView (vertical scrolling)
- item -> RecyclerView (horizontal scrolling) check view type is header or item with condition example : is object has type header
Ref : Google play store like interface using recycler view
My question is why do wrap recycler view into nested scroll view
Does it relate to smooth scroll of recycler view
Actually i am creating app which fetch 2 images and the scroll of recycler view in that is very slow so should i wrap it into nested scroll view for smooth flow or compress images and store them
I am a bit confused on this topic ?
Wrapping Recycler view in scroll view is like a two sided blade. You should be careful about using it.
because when you use it, the recycler view will loose its advantage of recycling unneeded rows so at the same time you will have references to all those view, so if you have rows with many graphical item it will make problem for slow devices.
If you see putting the recycler view inside another nested scrollview solved your speed problem, It means you do a mess in the adapter of recycler view.
Do not do any heavy process in adapters and onBindViewHolder
I have two layers of Recycler views, Main Recycler view contains dynamic Recycler views as items.
So, I need to click and assertion text inside items of inner Recycler views in Android Espresso, or any ideas.
I think it's must easier if I test inner recycler views separately