|
1 | 1 | package com.smarttoolfactory.home |
2 | 2 |
|
| 3 | +import android.widget.Toast |
| 4 | +import androidx.fragment.app.Fragment |
| 5 | +import androidx.fragment.app.activityViewModels |
| 6 | +import androidx.lifecycle.Observer |
| 7 | +import androidx.navigation.NavController |
| 8 | +import androidx.navigation.ui.AppBarConfiguration |
| 9 | +import androidx.navigation.ui.setupWithNavController |
| 10 | +import androidx.viewpager2.adapter.FragmentStateAdapter |
| 11 | +import androidx.viewpager2.widget.ViewPager2 |
| 12 | +import com.google.android.material.tabs.TabLayout |
| 13 | +import com.google.android.material.tabs.TabLayoutMediator |
3 | 14 | import com.smarttoolfactory.core.ui.fragment.DynamicNavigationFragment |
| 15 | +import com.smarttoolfactory.core.util.Event |
| 16 | +import com.smarttoolfactory.core.viewmodel.NavControllerViewModel |
| 17 | +import com.smarttoolfactory.home.adapter.HomeViewPager2FragmentStateAdapter |
4 | 18 | import com.smarttoolfactory.home.databinding.FragmentHomeBinding |
5 | 19 |
|
| 20 | +/** |
| 21 | + * Fragment that contains [ViewPager2] and [TabLayout]. |
| 22 | + * If this fragments get replaced and [Fragment.onDestroyView] |
| 23 | + * is called there are things to be considered |
| 24 | + * |
| 25 | + * * [FragmentStateAdapter] that is not null after [Fragment.onDestroy] cause memory leak, |
| 26 | + * so assign null to it |
| 27 | + * |
| 28 | + * * [TabLayoutMediator] cause memory leak if not detached after [Fragment.onDestroy] |
| 29 | + * of this fragment is called. |
| 30 | + * |
| 31 | + * * Data-binding which is not null after [Fragment.onDestroy] causes memory leak |
| 32 | + * |
| 33 | + * *[NavControllerViewModel] that has a [NavController] that belong to a NavHostFragment |
| 34 | + * that is to be destroyed also causes memory leak. |
| 35 | + */ |
6 | 36 | class HomeFragment : DynamicNavigationFragment<FragmentHomeBinding>() { |
7 | 37 |
|
8 | 38 | override fun getLayoutRes(): Int = R.layout.fragment_home |
| 39 | + |
| 40 | + private val navControllerViewModel by activityViewModels<NavControllerViewModel>() |
| 41 | + |
| 42 | + override fun bindViews() { |
| 43 | + |
| 44 | + // ViewPager2 |
| 45 | + val viewPager = dataBinding!!.viewPager |
| 46 | + |
| 47 | + // TabLayout |
| 48 | + val tabLayout = dataBinding!!.tabLayout |
| 49 | + |
| 50 | + /* |
| 51 | + Set Adapter for ViewPager inside this fragment using this Fragment, |
| 52 | + more specifically childFragmentManager as param |
| 53 | +
|
| 54 | + 🔥 Create FragmentStateAdapter with viewLifeCycleOwner |
| 55 | + https://stackoverflow.com/questions/61779776/leak-canary-detects-memory-leaks-for-tablayout-with-viewpager2 |
| 56 | + */ |
| 57 | + viewPager.adapter = |
| 58 | + HomeViewPager2FragmentStateAdapter(childFragmentManager, viewLifecycleOwner.lifecycle) |
| 59 | + |
| 60 | + dataBinding!!.toolbar.inflateMenu(R.menu.menu_home) |
| 61 | + |
| 62 | + dataBinding!!.toolbar.setOnMenuItemClickListener { |
| 63 | + if (it.itemId == R.id.menu_item_sort) { |
| 64 | + Toast.makeText(requireContext(), "Toast", Toast.LENGTH_SHORT).show() |
| 65 | + true |
| 66 | + } |
| 67 | + |
| 68 | + false |
| 69 | + } |
| 70 | + |
| 71 | + // Bind tabs and viewpager |
| 72 | + TabLayoutMediator(tabLayout, viewPager, tabConfigurationStrategy).attach() |
| 73 | + |
| 74 | + subscribeAppbarNavigation() |
| 75 | + } |
| 76 | + |
| 77 | + private fun subscribeAppbarNavigation() { |
| 78 | + navControllerViewModel.currentNavController.observe( |
| 79 | + viewLifecycleOwner, |
| 80 | + Observer { it -> |
| 81 | + |
| 82 | + it?.let { event: Event<NavController?> -> |
| 83 | + event.getContentIfNotHandled()?.let { navController -> |
| 84 | + val appBarConfig = AppBarConfiguration(navController.graph) |
| 85 | + dataBinding!!.toolbar.setupWithNavController(navController, appBarConfig) |
| 86 | + } |
| 87 | + } |
| 88 | + } |
| 89 | + ) |
| 90 | + } |
| 91 | + |
| 92 | + override fun onDestroyView() { |
| 93 | + |
| 94 | + // ViewPager2 |
| 95 | + val viewPager2 = dataBinding!!.viewPager |
| 96 | + // TabLayout |
| 97 | + val tabLayout = dataBinding!!.tabLayout |
| 98 | + |
| 99 | + /* |
| 100 | + 🔥 Detach TabLayoutMediator since it causing memory leaks when it's in a fragment |
| 101 | + https://stackoverflow.com/questions/61779776/leak-canary-detects-memory-leaks-for-tablayout-with-viewpager2 |
| 102 | + */ |
| 103 | + TabLayoutMediator(tabLayout, viewPager2, tabConfigurationStrategy).detach() |
| 104 | + |
| 105 | + /* |
| 106 | + 🔥 Without setting ViewPager2 Adapter to null it causes memory leak |
| 107 | + https://stackoverflow.com/questions/62851425/viewpager2-inside-a-fragment-leaks-after-replacing-the-fragment-its-in-by-navig |
| 108 | + */ |
| 109 | + viewPager2?.let { |
| 110 | + it.adapter = null |
| 111 | + } |
| 112 | + |
| 113 | + // Remove menu item click listener |
| 114 | + dataBinding!!.toolbar.setOnMenuItemClickListener(null) |
| 115 | + |
| 116 | + super.onDestroyView() |
| 117 | + } |
| 118 | + |
| 119 | + private val tabConfigurationStrategy = |
| 120 | + TabLayoutMediator.TabConfigurationStrategy { tab, position -> |
| 121 | + when (position) { |
| 122 | + 0 -> tab.text = "Flow" |
| 123 | + 1 -> tab.text = "RxJava3" |
| 124 | + else -> tab.text = "Flow+Pagination" |
| 125 | + } |
| 126 | + } |
9 | 127 | } |
0 commit comments