> Isn't that just done by specifying different values for different > states? Just like you would for a custom button? Doesn't look very > difficult in the source: > http://android.git.kernel.org/?p=platform/frameworks/base.git;a=blob;f=core/res/res/drawable/tab_indicator.xml;h=65df805d73ed4e759fe3f856bd5f6731bdb02ab0;hb=eclair > http://android.git.kernel.org/?p=platform/frameworks/base.git;a=blob;f=core/res/res/color/tab_indicator_text.xml;h=5f5c2a4a265fbbb0663fdec2bae4363cefaed92d;hb=eclair
Thank you. Now I am going to kvetch: This appears to point out one of the serious problems with this platform. Even doing very simple things require that one delve into the Android source code, as you did. The developer new to Android sees: http://developer.android.com/reference/android/widget/TabHost.html http://developer.android.com/reference/android/widget/TabHost.TabSpec.html As you can see, when it actually comes to anything other than the types of arguments to pass to methods, the documentation is of no help whatsoever. What these classes expect of the caller is left undefined. The developer wants to get from point A to point B, and that excursion should not need to stray into android.git.kernel.org for tasks as simple as this. P. V. Nasby -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
