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

by Arron » Sat, 30 Jan 2010 18:10:19 GMT

Sponsored Links
 Well that's exactly the reason why absoluteLayout was deprecated.  It
works for only one screen size.

I will say use various layouts with sp margins to space out the
buttons correctly.


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.



Sponsored Links

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

by kaasinees » Tue, 02 Feb 2010 02:07:56 GMT

 try making a new view that is centered in the layout than use the
margin attributes like mentioned before to position the buttons inside
that  view.

this way it could work on all screen sizes.


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

by James Wang » Sat, 27 Feb 2010 12:30:43 GMT

 I think you can do anything with Framelayout like absolutelayout.


Other Threads

1. <merge> with multiple ImageViews?

Anyone know if <merge>  works with multiple images:  header.xml =

<merge xmlns:android="">
<ImageView android:id="@+id/ImageView02" android:background="@drawable/imagex" 
<ImageView android:id="@+id/ImageView01" 

A constraint of <merge> is that it must be in the XML root tag, so we place the 
above in one file and then use <include> to import.

Another contraint is that it does not work with some Layouts like LinearLayout 
but the docs do state it works with FrameLayout


<FrameLayout android:id="@+id/FrameLayout01" android:layout_width="fill_parent" 
   <include android:layout_width="fill_parent" layout="@layout/header" />

Oddly enough this traps when displaying/running. Most examples are merging 
different types but not two images.

Any insight on this ???


2. Plans for Change (Was: Petition: Google, please improve the Android Market.)

I repeat this every time this is mentioned. **YOU CAN COMMENT ON YOUR OWN
PAID APP**. I do it all the time. If you have your app installed on your
device the Android Market will detect it as "Installed" and allow you to
rate it and comment it as if you purchased it. Your app may not always show
up in your Downloads list, so you may have to search for it, but it works.
(I'm using G1 with 1.6).

That being said, I do not agree that this is a good way to respond to
comments. You can only have one comment up at a time so trying to respond to
hundreds if not thousands of comments in this fashion is simply ridiculous.

I agree with you 100%. As is I have to butcher the English language and
leave out features due to the lack of space. Why it's so difficult to
increase this limit is simply baffling.

TreKing - Chicago transit tracking app for Android-powered devices


3. App2sd partisi sdcard

4. Android developers in Houston

5. read phone state and "identity"?

6. anyone interested in ThumbEE port of Dalvik?

7. Preferences for input method