Re: [android-developers] Re: When to set android:anyDensity to what value?

2011-04-11 Thread lbendlin
Our application is used when driving, and spends most of its life as a service, Not a single user has yet complained about grainy or jagged images, menu icons or some such in the UI part. The service occasionally shows custom toasts that cover the whole screen, and for these we use 300x300

Re: [android-developers] Re: When to set android:anyDensity to what value?

2011-04-11 Thread Kostya Vasilyev
11.04.2011 14:58, lbendlin пишет: Our application is used when driving, and spends most of its life as a service, Not a single user has yet complained They don't want to risk their life by looking closer :) about grainy or jagged images, menu icons or some such in the UI part. The service

Re: [android-developers] Re: When to set android:anyDensity to what value?

2011-04-11 Thread lbendlin
That's exactly the point. Mobile utility applications have very short UI usage cycles. Users usually don't take the time to look for that jagged edge, they get the information they need and carry on. (Having said that I still get wound up each time I look at the built in Android web browser

[android-developers] Re: When to set android:anyDensity to what value?

2011-04-10 Thread MarcoAndroid
So I should set it to true even when my app doesn't include resources to accommodate any screen density (suppose I'm lazy so I don't create any size- or density specific resources)? I'm wondering this because taken from:

[android-developers] Re: When to set android:anyDensity to what value?

2011-04-10 Thread MarcoAndroid
In short: am I always safe with anyDensity=true as long as I use dp and sp as I read in Table 2 here: http://developer.android.com/guide/practices/screens_support.html: 'That is, as long as your application uses density-independent units (dp) for screen layout sizes, then it will perform

Re: [android-developers] Re: When to set android:anyDensity to what value?

2011-04-10 Thread Kostya Vasilyev
There are really two related things here: 1 - Setting anyDensity to true or minSdk/targetSdk to 4 or above means that your application sees the real screen size/resolution/density at runtime. Android will scale your images as needed when they are loaded, so you won't get missing resource

Re: [android-developers] Re: When to set android:anyDensity to what value?

2011-04-10 Thread lbendlin
I have minSDK set to 3, anyDensity to true, and have just a single resource folder. Works fine for all devices from 1.5 all the way up to 3.x -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to

[android-developers] Re: When to set android:anyDensity to what value?

2011-04-10 Thread Zsolt Vasvari
Can't imagine that would look very good on an XHDPI screen. On Apr 11, 6:57 am, lbendlin l...@bendlin.us wrote: I have minSDK set to 3, anyDensity to true, and have just a single resource folder. Works fine for all devices from 1.5 all the way up to 3.x -- You received this message because

Re: [android-developers] Re: When to set android:anyDensity to what value?

2011-04-10 Thread Dianne Hackborn
Well you'll get 2x doubled images... but the screen itself is 2x the density of an mdpi screen, so the app's icons will mostly just look like they are on an mdpi screen. :} On Sun, Apr 10, 2011 at 5:49 PM, Zsolt Vasvari zvasv...@gmail.com wrote: Can't imagine that would look very good on an