In fairness, Cameron, the docs don't actually say that
android:anyDensity=false causes resources to be pulled from mdpi.
The documentation for that attribute is buried in the middle of the
Support for Multiple Screens page, and mostly talks about pixel
density math. The confusion is compounded by
This is from the Android Dev Guide http://developer.android.com/guide/
practices/screens_support.html
Pre-scaling of resources (such as image assets)
For example, if the current screen's density is high, the platform
loads resources that are tagged with the qualifier hdpi and uses them
without
Again, if you want to support multiple densities DON'T SAY YOU DON'T SUPPORT
THEM. Seriously! :) The first thing to do is get rid of
android:anyDensity=false so the system doesn't try to make your app think
it is running in mdpi.
If you still have problems after that, then we can talk about
3 matches
Mail list logo
