>> It is what I got working way back when, though I think 65px may be a
>> better height, and I have not yet tested the theory on QVGA, native 1.6
>> <uses-screens>, and whatnot.
>>
>> I'm going to be doing some more research on tabs in different screen
>> resolutions tomorrow (for a new chapter in a new edition of one of my
>> books). If you think of it, reply on this thread in 24 hours, and I'll
>> post a summary of my findings.
>
> ping :-)
I ask for 24 hours, I get 17 or so. Everybody's in such a rush... ;-)
So far, I can tell you:
-- Skipping the 62px of padding and using a LinearLayout to stack the
TabWidget and FrameLayout is now working. So, you can have a TabHost
hold a LinearLayout which holds the TabWidget and FrameLayout.
-- I am seeing no particular impacts on the tab size for different
screen resolutions, but I am still struggling with the whole screen
resolution support thing.
> i'm not seeing a ton of customisation options for the tab widget
You can customize the tabs somewhat via setView() on the TabSpec in 1.6,
though I have not tried this.
--
Mark Murphy (a Commons Guy)
http://commonsware.com | http://twitter.com/commonsguy
Android Development Wiki: http://wiki.andmob.org
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
No comments:
Post a Comment