Also these libraries don’t take advantage of DiffUtil. For complex lists, generic notifyDataSetChanged method will be called during updation.You are forced to keep layout and view references inside the model class itself. View holder creation and binding has to be written inside the data model.Your data objects should extend/implement from library's model, which can interfere with your object hierarchy.But such libraries have a common restrictions - Your data model will be polluted with the view logic.
To solve the above problems, you can also use a different library or libraries.
If the data needs to be updated, its hard to write the updation logic and call the correct notify method. If you have to add multiple viewtypes the code grows painfully. In default adapter approach, code is not re-usable as it is. What if you had to add all of these inside a single adapter. If you answered yes, then you must know how hard it is to do any one of these. Have you ever displayed multiple view types inside a single adapter? Have you ever added selection mode to an adapter? Have you ever set different span size to different items inside a single adapter? Have you ever added swipe-to-dismiss / drag & drop / infinite scrolling features to your adapter? v3.0 is identical to v2.0 except for package name changes and androidx support. Apart from this, MultiViewAdapter adds many other useful features into the library as add-ons. Using the library you will be able to build composable view holders, which can be re-used across your app. MultiViewAdapter makes it easy for you to create adapter with multiple view types easily. But creating adapters with multiple view types is always exhausting. Recyclerview is one of the powerful widgets inside android framework.
0 kommentar(er)
