On Tue, Nov 10, 2009 at 5:03 PM, freezy <[email protected]> wrote: > Of course, that's the whole point of density based *layouts*. But then, > that's why you specify "dip"s in your layout, so Android scales your button > accordingly. Only that you probably don't want to have the same *bitmap*used > for the different sizes that are rendered by Android.
Resources are just resources, the resource system doesn't define semantics for bitmaps or layouts. Each resource can be selected based on a large number of configurations (locale, mnc, orientation, whether there is a hard keyboard, dpad, trackball, screen size class, screen density, etc); you just use the ones that make sense for whatever your resource is. Btw unfortunately there is a bad bug in 2.0 where the resource version selection does not work correctly, and is using equivalence instead of >=. So you will need to use both -v4 and -v6 resources to work both places (the -v6 instead of -v5 is another bug). This will be fixed in a future update to Droid, at which point it should no longer be an issue as no other device should ship with the original 2.0 code that is currently on Droid. -- 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
