On Wed, Jun 16, 2010 at 2:31 PM, blab <[email protected]> wrote:
> Is there a way to prevent aapt v2.2 from "automatically including the > appropriate minimum version for new configurations, so that older > platforms do not see them"? > Explicitly supply your own version. > Due to this sneaky aapt behavior we simply cannot use 2.2 SDK as we > either will loose 1.5 support or increase our APK size by 40%. > This isn't true. Older platforms will not see the resources that were added for newer platforms. Just make sure there is a default resource value for all of your resources. > All image resources in our game are placed in "drawable-hdpi" folder. > Such structure gives us the minimum APK size with the highest quality > of images. > This also causes devices with lower density screens to have to scale all of your images, which can significantly impact performance. I strongly recommend against this. And Android 1.5 does NOT support this scaling. > This worked very well until 2.2. SDK. Although Android 1.5 does not > "know" about "hdpi" postfix it nevertheless magically knows that it > needs to scale the images down by factor of 1.5 (from hdpi to mdpi). > You got lucky. Android 1.5 was never documented to support different densities, and I can guarantee you that there are serious bugs in what it might do with them. -- Dianne Hackborn Android framework engineer [email protected] Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. -- 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
