Romain, could explain bit more pl..
fillparent - must be doing exactly the same thing.
Regards,
Nagendra
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email t
or you could modify this source efectively...but the solution is not
popular...:)
On Mon, May 4, 2009 at 10:40 PM, Romain Guy wrote:
>
> No, it does not make sense to take the parent's value.
>
> On Sun, May 3, 2009 at 11:28 PM, Raja Nagendra Kumar
> wrote:
> >
> > ok,
> >
> > In absence global
No, it does not make sense to take the parent's value.
On Sun, May 3, 2009 at 11:28 PM, Raja Nagendra Kumar
wrote:
>
> ok,
>
> In absence global defaults, could it take the same values as the
> parent (container).. so that UI developer could add these attributes
> only one it is different than p
ok,
In absence global defaults, could it take the same values as the
parent (container).. so that UI developer could add these attributes
only one it is different than parent..
Regards,
Raja Nagendra Kumar,
C.T.O
www.tejasoft.com
--~--~-~--~~~---~--~~
You recei
> All the view components does take layout_height, layout_width
> attributes.. and most of the time the valid value for them (in righly
> coded views) is fill_parent.
fill_parent is not more common than wrap_content, it depends on your
UI. There is no default, you must specify these params.
--
There is no default, a value must be supplied. And I don't think
fill_parent is significantly more common than wrap_content.
On Sat, May 2, 2009 at 7:51 AM, Raja Nagendra Kumar <
nagendra.r...@tejasoft.com> wrote:
>
> All the view components does take layout_height, layout_width
> attributes.. a
6 matches
Mail list logo