Library’s ResourcesCompat and ContextCompat classes as well. Theme attributes specified in the ColorStateList will be resolved usingĪdditional convenience methods were also added to Context and to the support Returns the ColorStateList associated with the passed in resource ID. Resolved using the passed in Theme argument. If the resourceĪny theme attributes specified in the ColorStateList will be
Returns the color associated with the passed in resource ID. Which introduced two new methods for extracting ColorStateLists from XML: Specifying theme attributes in ColorStateList XML files was not supported until API 23, Theme attributes such as R.lorAccent and R.lorPrimary on their own.
Theme in your app, and as a result, they will be unable to resolve the values pointed to by The problem is that Resources objects are not intrinsically linked to a specific W/Resources: ColorStateList color/button_text_csl has unresolved theme attributes!Ĭonsider using Resources.getColorStateList(int, Theme)Īt .getColorStateList(Resources.java:1011) R.lorAccent and R.lorPrimary theme attributes respectively: TextView, its disabled and enabled text colors should take on the colors pointed to by the To understand why these methods were deprecated in the first place, consider theĬolorStateList declared in XML below. “When will these two methods break my code?” ID points to a ColorStateList, the method will return the ColorStateList’s Returns the color associated with the passed in color resource ID. Offer that didn’t exist before? The problem with Resources#getColor(int) & Resources#getColorStateList(int)įirst, let’s be clear on what these old, deprecated methods actually do: But what is actually going on here? Why were these methodsĭeprecated in the first place and what do the new Theme-aware methods have to
0 kommentar(er)
