Layout problems: AbsoluteLayout deprecated, how to do it now?

by theSmith » Sun, 31 Jan 2010 03:28:44 GMT

You should be able to use a relativelayout or a linearlayout and just
add padding in dip (density independent pixels) to the sides of the
buttons. For small screen devices you probably want to create a new
layout with smaller buttons so it displays properly.
-theSmith
--

Hi,
I am having problems getting Android to use the correct resources.
I am trying to have it pick the correct resources across all densitys
and screen layouts & orientations.
So I have created the directory structure as follows
drawable
drawable-large
drawable-large-land
drawable-large-port
drawable-normal-hdpi
drawable-normal-mdpi
drawable-normal-ldpi
drawable-normal-land-hdpi
drawable-normal-land-mdpi
drawable-normal-land-ldpi
drawable-normal-port-hdpi
drawable-normal-port-mdpi
drawable-normal-port-ldpi
drawable-small
drawable-small-land
drawable-small-port
Since large screen layouts are always hi res screens (480x800,480x848)
and small screen layouts are always lowres(240x320,240x400 etc) i did
not include density descriptions in the directory naming.
And likewise since normal can be low,medium of high resolution
screens, I have included all the different density markers.
I am not sure if android likes me naming the directories like this
since when I load up the normal 320x480 screen,
It is selecting Hi-res resources and down-scaling them. I can see
nowhere in documentation that says this is what it will do so im am
quite confussed as this is what it seems like it is doing.
I am using
<supports-screens
android:largeScreens="true"
android:normalScreens="true"
android:smallScreens="true"
android:anyDensity="true" />
Yet I am positive it is resizing the resources automatically for me.
Testing with 2.0 emulators.
When using the WVGA emulators, it uses the hdpi resources unscaled,
when using the 320x480 emulator, it is using the hdpi resources down-
scaled.
Any ideas on where I am going wrong?
--