Thanks for the info!

You're welcome!

use tab layout with fragment

Thanks you too :)

Thanks! The viewpager2 uses a normal recyclerview adapter. If you use viewpager1 then you can use the FragmentStateAdapter

in my case i'm using viewpager2 , so i need to make a class that recyclerview adapter, and another little question if you dont mind , i m usin third party library called smarttablayout , is there way to pass that in tablayoutmediator because apparently it only takes the normal tablayout thank you

So I don't know that library, but if that custom tablayout is a subclass of tablayout then it should actually work to pass it to the mediator

it is actually a library and when i passed it , it said require tablayout , and mine is smarttablayout

Then it might be an older library that doesn't work with the new viewpager2. Then you need to use it with viewpager1 and create a fragmentstateadapter

You mean you want to show two toasts one after another?

@@PhilippLackner No No, i just tried your code same. But when i clicked one tab after the another tab. it tried to show multi toast in same time. for example it shows "Unselected tab2" and "Selected tab1" so they are mixing.

@@valarmorghulisx yes that can happen when you show them at the same time. In production you should of course avoid this, I just wanted to show how the different events work here 👍

@@PhilippLackner ohh thank you so much :)

Thanks Alice. This was helpful

I have the same problem ... please help, how can we solve this?

Make sure you are using in activity_main.xml

Try This instead! val adapter = ViewPagerAdapter(images) findViewById(R.id.viewPager).adapter = adapter TabLayoutMediator(findViewById(R.id.tabLayout),findViewById(R.id.viewPager)){ tab , position -> tab.text = "Tab ${position+1}" }.attach()

Are you doing the API call on a different thread?

Hi @@mikec4220 ! Thanks for replying. The webservice call is made on backgorund thread only. I found that, I am receiving 1000 records from Webservice which I need to populate recyclerview. No paging mechanism implemented from backend. The screen is getting stuck when applying all data to adapter. What I tried is I initialized adapter with empty data before making Webservice call. After receiving data from Webservice , I just updated data to a method in Adapter and called notifyDataSetChanged(). It looked ok as of now but still screen stucks a bit. Any idea on how to handle this kind of stituation from Mobile side if backend does not have paging mechanism.

Hi @@chandrasaimohanbhupathi7837 , I'm learning the ropes myself and by the look of it you are getting this behaviour because you're loading too much data. I believe the pagination was developed to solve this particular issue you are encountering. Also notifyDataSetChanged() is not the best to use with recyclerviews, not in this case at least, my understanding is that it will refresh all the views instead of only the ones needed. Look at diffutils, Phillip has a good example when he is setting up RecyclerView for the NewsApp. Hope this helps!