Hi William, I will suggest you to use layout weight/ weight sum ( basically instead if giving dip value, give in percentage)
Moktarul Anam On Feb 22, 7:08 am, William Ferguson <william.ferguson...@gmail.com> wrote: > I am trying to work out why a device (in this case an AVD) that is > 800*400 and mdpi is selecting a layout that is large-hdpi. > > There are only 2 layout options for the app, the default and large- > hdpi. > I can conceivably see how the device could be considered large > - large screens are at least 640dp x 480dp > (fromhttp://developer.android.com/guide/practices/screens_support.html#range) > even though it's not quite there is one dimension. > > But it's only 160dpi, so certainly not hdpi (ie approx 240dpi). > > I had always thought that in order to match a resource qualifier > (including layout) you need to at least match all items. So I expected > this to fail to match based on density. Is my understanding incorrect? > Is it actually trying to do a nearest match or best fit and is > determining that large-hdpi is the closest fit for large-mdpi? > > It's almost like it has ignored density altogether when choosing the > layout. > > Is there a way to programatically determine which resource selectors > have been used to choose layout? > > William -- 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
