From 09acb7ca897c9f49dd65b7173688e4ca63ca5dd3 Mon Sep 17 00:00:00 2001 From: Dianne Hackborn Date: Thu, 17 Oct 2013 17:28:09 -0700 Subject: =?UTF-8?q?Fix=20issue=20#11256132:=20Add=20density=20bucket=20for?= =?UTF-8?q?=20all=20real=20numbers=20between=200=20and=20=E2=88=9E...?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Well, how about 400. 400 is a real number. Change-Id: I29ac61b7d629d582c7b68367365a7f81fcf679a2 --- core/java/android/util/DisplayMetrics.java | 8 ++++++++ 1 file changed, 8 insertions(+) (limited to 'core/java/android') diff --git a/core/java/android/util/DisplayMetrics.java b/core/java/android/util/DisplayMetrics.java index dae47b8..6cda905 100644 --- a/core/java/android/util/DisplayMetrics.java +++ b/core/java/android/util/DisplayMetrics.java @@ -67,6 +67,14 @@ public class DisplayMetrics { public static final int DENSITY_XHIGH = 320; /** + * Intermediate density for screens that sit somewhere between + * {@link #DENSITY_XHIGH} (320dpi) and {@link #DENSITY_XXHIGH} (480 dpi). + * This is not a density that applications should target, instead relying + * on the system to scale their {@link #DENSITY_XXHIGH} assets for them. + */ + public static final int DENSITY_400 = 400; + + /** * Standard quantized DPI for extra-extra-high-density screens. Applications * should not generally worry about this density; relying on XHIGH graphics * being scaled up to it should be sufficient for almost all cases. -- cgit v1.1