EDIT : According to the ItemAnimator documentation : This class defines the animations that take place on items as changes are made to the adapter. So unless you add your items one by one to your RecyclerView and refresh the view at each iteration, I don’t think ItemAnimator is the solution to your need. Here … Read more
Add android:textColorLink=”yourcolorhere” to your TextView
Finally, I have found a solution. It simply consists of overriding the value for colorControlActivated, colorControlHighlight and colorControlNormal in your app theme definition and not your edittext style. Then, think to use this theme for whatever activity you desire. Below is an example: <style name=”Theme.App.Base” parent=”Theme.AppCompat.Light.DarkActionBar”> <item name=”colorControlNormal”>#c5c5c5</item> <item name=”colorControlActivated”>@color/accent</item> <item name=”colorControlHighlight”>@color/accent</item> </style>
I had a (possibly) related issue – entering a new instance of an activity with a RecyclerView, but with a smaller adapter was triggering this crash for me. RecyclerView.dispatchLayout() can try to pull items from the scrap before calling mRecycler.clearOldPositions(). The consequence being is that it was pulling items from the common pool that had … Read more
use NestedScrollView instead of ScrollView Please go through NestedScrollView reference document for more information. and add recyclerView.setNestedScrollingEnabled(false); to your RecyclerView
I needed to be using setCompoundDrawablesWithIntrinsicBounds.
@Asahi pretty much hit the nail on the head, but I just wanted to add a bit of XML for anyone maybe floating in here later via google: <ListView android:id=”@+id/MyListView” android:layout_height=”match_parent” android:layout_width=”match_parent” android:divider=”@android:color/transparent” android:dividerHeight=”10.0sp”/> For some reason, values such as “10”, “10.0”, and “10sp” all are rejected by Android for the dividerHeight value. It wants … Read more
Found the solution myself in the end. The problem was not with the LinearLayout, but with the ScrollView (seems weird, considering the fact that the ScrollView was expanding, while the LinearLayout wasn’t). The solution was to use android:fillViewport=”true” on the ScrollView.
Java LinearLayout.LayoutParams params = new LinearLayout.LayoutParams(LayoutParams.WRAP_CONTENT, LayoutParams.MATCH_PARENT); params.weight = 1.0f; params.gravity = Gravity.TOP; button.setLayoutParams(params); Kotlin val params = LinearLayout.LayoutParams( LinearLayout.LayoutParams.WRAP_CONTENT, LinearLayout.LayoutParams.WRAP_CONTENT ).apply { weight = 1.0f gravity = Gravity.TOP } For gravity values and how to set gravity check Gravity. Basically, you should choose the LayoutParams depending on the parent. It can be RelativeLayout, LinearLayout … Read more
<merge/> is useful because it can get rid of unneeded ViewGroups, i.e. layouts that are simply used to wrap other views and serve no purpose themselves. For example, if you were to <include/> a layout from another file without using merge, the two files might look something like this: layout1.xml: <FrameLayout> <include layout=”@layout/layout2″/> </FrameLayout> layout2.xml: … Read more