On 03/10/2012 01:20 AM, jtoolsdev wrote:
I probably need to continue the thread where this was discussed back
at the start of February. I'm certainly not the only one who is
confused about how the supports-screens qualifiers work. I would also
ask a way that we can test them before we actually release an APK.
This only effects the filtering on the "Market" (or "Play") so you
don't really know for sure if the qualifiers are working properly. Or
maybe a tool could be released so we can check locally before
release. And since I created the app there have been more qualifiers
added. To put it simply I want the users with screens less than 10"
to get the tabbed version even if they have a higher density screen.
According to this guide:
http://developer.android.com/guide/practices/screens_support.html
... a typical 10" 1280x800 screen is xlarge, while a typical 7" 1024x600
screen is just large, without the x.
This should be enough to do the filtering you require.
Since you don't have a 7" device, you could ask one of your users (if
there are any you can get in touch with), to install one of the
countless screen metrics reporting apps to verify the device's resource
qualifiers.
One more thing: some custom firmwares let the user change the screen's
density - if someone deciced to run 1024x600 at 120dpi, that would be an
xlarge, rather than just large, screen.
Finally, there are new, dp-based Market (er, Play) filters that are
similar to the dp-based resource qualifiers introduced in 3.2, described
here:
http://developer.android.com/guide/topics/manifest/supports-screens-element.html#requiresSmallest
.. but it says that they are not currently supported by Market (er, Play).
-- K
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
