On Wed, Oct 21, 2009 at 4:09 PM, Artem <[email protected]> wrote: > Somehow, we are trying this and it does not seem to be working. > Namely, it seems > Donut *does not* pick up new resolution images in compatibility mode. >
I am pretty positive it does. Proof: when you run any existing application on a high density display, you will get the nice high density graphics for any buttons or other stock widgets. This is because the framework is picking the correct density graphics for the screen. Note, however, that this can only happen if you are loading the image as a Drawable from Resources, since there is special magic in BitmapDrawable and NinePatchDrawable to load the bitmap based on the true screen report to the app metrics that match the compatibility scaling it is. Also, if you draw anything into an off-screen bitmap, then you will force everything in to the compatibility scaling and lose any high-density graphics. As a general rule, the compatibility modes are only there for existing applications that were written before knowing about multiple screens. The first thing you should do is turn them off. I don't really understand why you are trying to keep your app running in compatibility mode on 1.6; that is by and large really what you -don't- want. -- 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 -~----------~----~----~----~------~----~------~--~---
