Keep in mind that all densities are a potential match, and screen size is considered a more significant match than density. So if there is the choice between resources with two different densities, but one has a better match for the screen size, the screen size will win.
And I will say what I usually do -- I very strongly recommend mixing screen size and screen density qualifiers in the same configuration. These are two * orthogonal* axis. You will need to think very hard and long about the set of different screens that are going to match the qualifiers you have, and I think it most cases this is *not* what people are thinking. Usually people do this because they think they are more finely-tuning to try to design for a specific screen resolution, but that is not what this does. On Thu, Feb 23, 2012 at 1:48 PM, William Ferguson < william.ferguson...@gmail.com> wrote: > Thanks for the review Mark. > I didn't think I was going insane, just tearing my hair out. > > William > > > On Feb 23, 11:15 pm, Mark Murphy <mmur...@commonsware.com> wrote: > > Replying to the list: > > > > On Thu, Feb 23, 2012 at 2:54 AM, William Ferguson > > > > <william.ferguson...@gmail.com> wrote: > > > you can download a very small project showing this behaviour from > > > [REDACTED] > > > Deploy it to a 2.2 (I haven't tested other Android Version but I > > > expect the same) AVD with a resolution of WVGA800 (800*400) and > > > default "Abstracted LCD density" of 160dpi (ie mdpi). > > > The buttons will show the text for large hdpi. > > > > Well, I can reproduce the problem, on multiple Android emulator > > versions (including 4.0) and the original Galaxy Tab 7. > > > > In the sample you sent me, it pulls from res/layout-large-port-hdpi/ > > > > If I add a res/layout-large-port-mdpi/ directory, that gets used on a > > 4.0 emulator and the 2.2 emulator, but not the Tab 7. > > > > That's indicative of a bug in the Tab 7: > > > > http://stackoverflow.com/questions/7049659/understanding-samsung-gala... > > > > In terms of why it pulls from res/layout-large-port-hdpi/ instead of > > res/layout-xlarge-port/ or res/layout-port/, I cannot say. > > > > -- > > Mark Murphy (a Commons Guy)http://commonsware.com| > http://github.com/commonsguyhttp://commonsware.com/blog|http://twitter.com/commonsguy > > > > Android Training...At Your Office:http://commonsware.com/training > > -- > 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@googlegroups.com > To unsubscribe from this group, send email to > android-developers+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en > -- Dianne Hackborn Android framework engineer hack...@android.com 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 android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
