Difference between View margin and padding , mPadding and mUserPadding?

by GPU » Fri, 30 Oct 2009 18:43:54 GMT


Sponsored Links
 Difference between View margin and padding , mPadding and mUserPadding?
--~--~---------~--~----~------------~-------~--~----~



Difference between View margin and padding , mPadding and mUserPadding?

by Mark Murphy » Fri, 30 Oct 2009 20:16:01 GMT


 


For the purposes of determining the boundaries of a background, padding
is considered "inside" the widget (and so padding area gets the
background) and margin is "outside" the widget (and so does not get the
background).

-- 
Mark Murphy (a Commons Guy)
 http://commonsware.com  |  http://twitter.com/commonsguy 

Android Development Wiki:  http://wiki.andmob.org 

--~--~---------~--~----~------------~-------~--~----~


Sponsored Links


Other Threads

1. Look and Feel, Example, Spinner: more parameters or source code?

In the first part of the challenge, pressed for time, I selected from
UI elements provided in the demo kit thinking that this would be the
best way to adhere to emerging look and feel expectations and still
meet the deadline. I wasn't able to get the spinner to do what I
wanted - don't recall if it was word wrap or less padding to get more
on a screen... something like list6 but where you could make choices
while seeing the context of all your previous choices. Anyway, I went
with dialog select and then had a desire to get a result from a void
code element, without rewriting it from scratch. A set of stacked
spinners that support word wrap (because of the narrow screen) and
have almost no padding to provide rich context like the collapsed
list
6  (or the gmail collapsed view we are all so familiar with) would
have been ideal.

There are 3 ways to get there that I see: 1) more parameters on the
spinner, 2) availible source code that can be modified hoping to not
corrupt the look and feel, and 3) a feature request for a new
standard
UI element.


Which of these ways gets us to the desired consistent, but more
powerful, UI destination while respecting the time priorities of all
involved?


Thank you for any thoughts here,


--~--~---------~--~----~------------~-------~--~----~

2. ook and feel, Spinner,... source code or more parameters?

In the first part of the challenge, pressed for time, I selected from
UI elements provided in the demo kit thinking that this would be the
best way to adhere to emerging look and feel expectations and still
meet the deadline. I wasn't able to get the spinner to do what I
wanted - don't recall if it was word wrap or less padding to get more
on a page... something like list6 but where you could make choices
while seeing the context of all your previous choices. Anyway, I went
with dialog select and then had a desire to get a result from a void
code element, without rewriting it from scratch. A set of stacked
spinners that support word wrap (because of the narrow screen) and
have almost no padding to provide rich context like the collapsed list
6  (or the gmail collapsed view we are all so familiar with) would
have been ideal.

There are 3 ways to get there that I see: 1) more parameters on the
spinner, 2) availible source code that can be modified hoping to not
corrupt the look and feel, and 3) a feature request for a new standard
UI element.

Which of these ways gets us to the desired consistent but more
powerful UI destination?

Thanks,
--~--~---------~--~----~------------~-------~--~----~

3. About the Android Developer Challenge

4. Errors with attempt to create new Android Project in Eclipse

5. Android Back Button

6. Does it have a SIP stack.

7. DateInputMethod