layout_weight=1.0 will cause the view to fill any remaining space.
If the view in the middle might be bigger than the available space it
will push the bottom row off however. There's a solution for that.
Pent
--
You received this message because you are subscribed to the Google
Groups Android
24.12.2010 19:49, Pent пишет:
If the view in the middle might be bigger than the available space it
will push the bottom row off however. There's a solution for that.
This case can be correctly handled by using a RelativeLayout, as I just
described in my other message.
--
Kostya Vasilyev --
Thanks, I did finally get it done with a relative layout.
The only problem I ran into was making sure there were no forward references
in the id's. (Which is why your example had the middle layout at the
bottom.) I was just trying to modify my existing layout, and it had the
middle in the
24.12.2010 20:54, John Lussmyer пишет:
The only problem I ran into was making sure there were no forward
references in the id's. (Which is why your example had the middle
layout at the bottom.) I was just trying to modify my existing
layout, and it had the middle in the middle! :-) I had
I really think what you're trying to do is most easily expressed as a
LinearLayout (itself using width and height to fill parent) using the
layout_weight property to make the middle view grab any extra space.
If found that it's easy to go overboard with a verbose RelativeLayout
when all that's
The layout performance docs say that RelativeLayout is faster due to fewer
calls to calculate child dimensions.
I actually got it working with a fairly minimal layout definition.
On Fri, Dec 24, 2010 at 8:19 PM, Doug beafd...@gmail.com wrote:
I really think what you're trying to do is most
6 matches
Mail list logo
