Home | History | Annotate | Download | only in practices

Lines Matching full:navigation

15       <li><a href="#NavigatingUp">Using "up" navigation</a></li>
59 the app and provide user actions and navigation.</p>
101 items". You can also add navigation features to the action bar, such as tabs or a drop-down list,
194 update the action bar each time the fragments change, depending on what actions or navigation modes
201 allow the normal activity stack to handle back-navigation).</p>
381 action items may overlap with other action bar elements such as the title or navigation items.</li>
396 <li><strong>Avoid using custom navigation modes when possible</strong>. Use the built-in tab
397 and drop-down navigation modes when possible&mdash;they're designed so the system can adapt their
400 (this is known as the "stacked action bar"). If you must build a custom navigation mode or other
423 display action items on a narrow screen and also leave room for navigation and title elements
433 <p class="img-caption"><strong>Figure 3.</strong> Split action bar with navigation tabs on the left;
438 navigation tabs along with the split action bar, call {@link
441 so it disappears and all that?s left are the navigation tabs at the top and the action items at the
456 <h3 id="NavigatingUp">Using "up" navigation</h3>
459 developer guide, you can use the application icon in the action bar to facilitate user navigation
462 it might seem similar to the standard <em>Back</em> navigation in some cases, the up navigation
464 provides a more predictable navigation method for situations in which the user may have entered
468 extra consideration to how your up navigation behaves in each configuration. For example, when on a
470 navigation to go up to the parent screen, whereas it's not necessary when showing the same
473 <p>For more information about enabling up navigation, see the <a