Re: [android-developers] Re: VectorDrawable/BitmapDrawable in custom view.

2015-02-26 Thread Madis Pink
This happens because drawable-nodpi is a more specific configuration compared to drawable-v21. (See http://developer.android.com/guide/topics/resources/providing-resources.html#BestMatch and qualifier order of precedence in http://developer.android.com/guide/topics/resources/providing-resour

Re: [android-developers] Re: VectorDrawable/BitmapDrawable in custom view.

2015-02-25 Thread Nathan
Naming the folders drawable-nodpi-v17 and drawable-nodpi-v21 did do what I want it to do. Now it looks so much nicer on Android 5.0 than on 4.4. Nathan On Monday, February 23, 2015 at 2:17:30 PM UTC-8, Sérgio Faria wrote: > > Maybe if you move face.png to drawable-nodpi-v17 it will work > If

Re: [android-developers] Re: VectorDrawable/BitmapDrawable in custom view.

2015-02-23 Thread Sérgio Faria
Maybe if you move face.png to drawable-nodpi-v17 it will work If it doesn't work you can use the inflate method to force it. 2015-02-23 21:44 GMT+00:00 Nathan : > No ideas? > > In Android Wear, it is definitely using the vector drawable. > > In Nexus, 9, it is definitely using a raster one and the

[android-developers] Re: VectorDrawable/BitmapDrawable in custom view.

2015-02-23 Thread Nathan
No ideas? In Android Wear, it is definitely using the vector drawable. In Nexus, 9, it is definitely using a raster one and there appears to be now way to force it. Nathan -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this