Databases
StackOverflow2013
Postsdbo
POAndroid : ugly TABS in 2.0 vs 1.5 ... why ? where are my rounded corners TABS?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POAndroid : ugly TABS in 2.0 vs 1.5 ... why ? where are my rounded corners TABS?
    primarykey
    data
    text
    <p>I simply use the tabwidget :</p> <pre><code>mTabHost = getTabHost(); mTabHost.addTab(mTabHost.newTabSpec("tab_1").setIndicator(getString(R.string.day0)).setContent(R.id.tab1_content)); mTabHost.addTab(mTabHost.newTabSpec("tab_2").setIndicator(getString(R.string.day1)).setContent(R.id.tab2_content)); mTabHost.addTab(mTabHost.newTabSpec("tab_3").setIndicator(getString(R.string.day2)).setContent(R.id.tab3_content)); mTabHost.addTab(mTabHost.newTabSpec("tab_4").setIndicator(getString(R.string.day3)).setContent(R.id.tab4_content)); mTabHost.addTab(mTabHost.newTabSpec("tab_5").setIndicator(getString(R.string.about)).setContent(R.id.tab5_content)); mTabHost.setCurrentTab(0); </code></pre> <p>Why are my tabs so uggly in 2.0 (no more rounded corners as in 1.5/1.6) ?</p> <p><a href="http://img521.imageshack.us/img521/1823/ugglytabs.png" rel="nofollow noreferrer">ugly tabs here</a></p> <p>=></p> <p><a href="http://img42.imageshack.us/img42/3913/bettertabshere.png" rel="nofollow noreferrer">this was better</a></p> <p>What should I do now to show "rounded corners" TABS to Nexus One (for exemple) users ;-) ?</p> <p>Is it because of the following manifest lines :</p> <pre><code>&lt;uses-sdk android:minSdkVersion="3" android:targetSdkVersion="4" /&gt; &lt;supports-screens android:smallScreens="true" android:normalScreens="true" android:largeScreens="true" android:anyDensity="true" /&gt; </code></pre> <p>I have to keep <strong>android:anyDensity="true"</strong> otherwise I've got a problem with re-sizing of the menus described <a href="https://stackoverflow.com/questions/2264874/android-changing-locale-within-the-app-itself">here</a></p> <p>As a separate question, my users can change the Locale within my app itself, I then "redraw" the menus using onPrepareOptionsMenu (Menu menu) to refresh the strings within the menu with the new language choosen by the user. Is there an equivalent for TABS (I have local strings within the Title of the TABS) or do I have to delete all the tabs and re-create them from scratch ?</p> <p>Txs in advance for your help.</p> <p>Hub</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USHubert
    plurals
    1. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POAndroid : ugly TABS in 2.0 vs 1.5 ... why ? where are my rounded corners TABS?
      1. USItalo Borssatto
      1. VTFavorite
    2. VO
      singulars
      1. POAndroid : ugly TABS in 2.0 vs 1.5 ... why ? where are my rounded corners TABS?
      1. This table or related slice is empty.
      1. VTUpMod
    1. CODoes this have anything to do with Sense UI perhaps?
      singulars
      1. POAndroid : ugly TABS in 2.0 vs 1.5 ... why ? where are my rounded corners TABS?
      1. USsargas
    2. COI don't think so. It's like that in the Emulator for the Nexus one.
      singulars
      1. POAndroid : ugly TABS in 2.0 vs 1.5 ... why ? where are my rounded corners TABS?
      1. USHubert
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload