>The combination of width/height is also useful to impose
>a minimum size. For instance width=200dip + weight=1 means "take at
>least 200 dip and then the remaining space if available."
Thanks for the clarification, that's exactly what I was curious about.
Cheers,
- C
--
You received this mess
The framework supports both dp and dip, there's no reason to get rid
of either one. As for weight, ignoring the height/width is not a
solution. The weight is used to distribute the remaining empty space,
and the remaining empty space is computed by looking at the
width/height. The combination of wi
Hey Romain,
Speaking of LinearLayouts and density-independent pixels can you proclaim
once and for all whether, going forward, its going to be 'dip' or 'dp', or
will the framework always support both?
Sort of back on topic, can linear layouts with weighting simply ignore the
layout_[height|wid
0dip/weight=1 is a special case that LinearLayout can optimize. Also,
match_parent/weight=1.0 is (almost) meaningless. You are telling
LinearLayout to have this child take up all the space (match_parent)
and then fill the remaining available empty space (weight=1.0.) What
you really want is 0dip/we
Hi,
I have a linearlayout and one of its element was as follows
on running layoutopt on this it gave following message
"Use an android:layout_height of 0dip instead of match_parent for
better performance"
How does this help in getting better performance ?
I am using the following xml for a view:-
For this view, I got the following output from layoutopt tool
...This TableRow layout or its TableLayout parent is useless
I am not sure if I can remove TableRow or TableLayout. How can I solve
this? I don't want the TextView to be covered by Check
6 matches
Mail list logo
