From 4cad00b696a81d33ebf59c7418a3d0fb4ea089a7 Mon Sep 17 00:00:00 2001
From: Adam Lesinski
Date: Tue, 8 Sep 2015 14:16:49 -0700
Subject: Add anydpi to the providing-resources docs
Change-Id: Ic108d9da2e39b9f8581311fe610a1959a24a732f
---
docs/html/guide/topics/resources/providing-resources.jd | 9 +++++++--
1 file changed, 7 insertions(+), 2 deletions(-)
(limited to 'docs/html')
diff --git a/docs/html/guide/topics/resources/providing-resources.jd b/docs/html/guide/topics/resources/providing-resources.jd
index 6f9545d..68c44a4 100644
--- a/docs/html/guide/topics/resources/providing-resources.jd
+++ b/docs/html/guide/topics/resources/providing-resources.jd
@@ -646,7 +646,8 @@ application during runtime.
xxhdpi
xxxhdpi
nodpi
- tvdpi
+ tvdpi
+ anydpi
@@ -667,7 +668,11 @@ to match the device density.
- {@code tvdpi}: Screens somewhere between mdpi and hdpi; approximately 213dpi. This is
not considered a "primary" density group. It is mostly intended for televisions and most
apps shouldn't need it—providing mdpi and hdpi resources is sufficient for most apps and
-the system will scale them as appropriate. This qualifier was introduced with API level 13.
+the system will scale them as appropriate. Added in API Level 13
+ - {@code anydpi}: This qualifier matches all screen densities and takes precedence over
+other qualifiers. This is useful for
+vector drawables.
+Added in API Level 21
There is a 3:4:6:8:12:16 scaling ratio between the six primary densities (ignoring the
tvdpi density). So, a 9x9 bitmap in ldpi is 12x12 in mdpi, 18x18 in hdpi, 24x24 in xhdpi and so on.
--
cgit v1.1
|