Home
last modified time | relevance | path

Searched refs:back (Results 1 – 25 of 209) sorted by relevance

123456789

/frameworks/compile/mclinker/lib/Target/Mips/
DMipsGOT.cpp108 it->m_pLastLocal = llvm::cast<MipsGOTEntry>(&m_SectionData->back()); in finalizeScanning()
110 it->m_pLastGlobal = llvm::cast<MipsGOTEntry>(&m_SectionData->back()); in finalizeScanning()
161 m_MultipartList.back().m_Inputs.insert(m_pInput); in initGOTList()
171 m_MultipartList.back().m_Inputs.insert(m_pInput); in changeInput()
191 m_MultipartList.back().m_LocalNum + in isGOTFull()
192 m_MultipartList.back().m_GlobalNum; in isGOTFull()
212 m_MultipartList.back().m_LocalNum -= m_InputLocalSymbols.size(); in split()
213 m_MultipartList.back().m_GlobalNum -= uniqueCount; in split()
214 m_MultipartList.back().m_Inputs.erase(m_pInput); in split()
218 m_MultipartList.back().m_Inputs.insert(m_pInput); in split()
[all …]
/frameworks/base/docs/html/training/implementing-navigation/
Dtemporal.jd2 page.tags="back navigation","NavUtils","TaskStackBuilder"
14 <li><a href="#back-fragments">Implement Back Navigation for Fragments</a></li>
15 <li><a href="#back-webviews">Implement Back Navigation for WebViews</a></li>
21 <li><a href="{@docRoot}guide/components/tasks-and-back-stack.html">Tasks and Back Stack</a></li>
33 <p>In almost all situations, the system maintains a back stack of activities while the user
64 <p>Ordinarily, the system incrementally builds the back stack as the user navigates from one
67 back stack because the activity is running in a new task without any back stack at all.</p>
70 you should add activities into your task's back stack so that pressing <em>Back</em> navigates
120 {@link android.support.v4.app.NavUtils} APIs to synthesize a new back stack by identifying which
125 <h3 id="CreateBackStack">Create back stack when starting the activity</h3>
[all …]
Dancestral.jd21 <li><a href="{@docRoot}guide/components/tasks-and-back-stack.html">Tasks and Back Stack</a></li>
135 If the target parent activity is in the task's back stack, it is brought
158 requires that you create a new back stack.</p>
161 <h3 id="BuildBackStack">Navigate up with a new back stack</h3>
169 with the appropriate back stack before navigating up.</p>
189 // when navigating up, with a synthesized back stack.
191 // Add all of this activity's parents to the back stack
/frameworks/compile/mclinker/include/mcld/LD/
DRelocData.h79 reference back () { return m_Relocations.back(); } in back() function
80 const_reference back () const { return m_Relocations.back(); } in back() function
DSectionData.h72 reference back () { return m_Fragments.back(); } in back() function
73 const_reference back () const { return m_Fragments.back(); } in back() function
DELFSegment.h51 LDSection* back() { return m_SectionList.back(); } in back() function
52 const LDSection* back() const { return m_SectionList.back(); } in back() function
DEhFrame.h129 const CIE& cie_back () const { return *m_CIEs.back(); } in cie_back()
130 CIE& cie_back () { return *m_CIEs.back(); } in cie_back()
142 const FDE& fde_back () const { return *m_FDEs.back(); } in fde_back()
143 FDE& fde_back () { return *m_FDEs.back(); } in fde_back()
/frameworks/base/tools/layoutlib/bridge/src/com/android/layoutlib/bridge/bars/
DNavigationBar.java40 int back = 1; in NavigationBar() local
44 back = 3; in NavigationBar()
48 loadIcon(back, "ic_sysbar_back.png", density, isRtl); in NavigationBar()
/frameworks/compile/mclinker/lib/LD/
DEhFrame.cpp96 offset = m_pSectionData->back().getOffset() + m_pSectionData->back().size(); in addFragment()
106 offset = m_pSectionData->back().getOffset() + m_pSectionData->back().size(); in addFragment()
/frameworks/base/docs/html/distribute/promote/
Ddevice-art.jd179 landRes: ['shadow', 'back', 'fore'],
181 portRes: ['shadow', 'back', 'fore'],
193 landRes: ['shadow', 'back', 'fore'],
195 portRes: ['shadow', 'back', 'fore'],
207 landRes: ['shadow', 'back', 'fore'],
209 portRes: ['shadow', 'back', 'fore'],
220 landRes: ['shadow', 'back', 'fore'],
222 portRes: ['shadow', 'back', 'fore'],
234 landRes: ['shadow', 'back', 'fore'],
236 portRes: ['shadow', 'back', 'fore'],
[all …]
/frameworks/base/docs/html/training/design-navigation/
Dancestral-temporal.jd25 <li><a href="{@docRoot}guide/components/tasks-and-back-stack.html">Tasks and Back Stack</a></li>
49 you back at the Launcher, after which the <em>Back</em> button will do nothing.</p>
52 <img src="{@docRoot}images/training/app-navigation-ancestral-navigate-back.png"
54 id="figure-navigate-back">
61 the system handles <a href="{@docRoot}guide/components/tasks-and-back-stack.html">tasks and
62 the <em>back stack</em></a>, or the list of previous screens, automatically. The <em>Back</em>
68 to navigate between web pages, you may wish to trigger the embedded browser's default <em>back</em>
83 …ion, if they get lost in the app, they can select <em>Home</em> to arrive back at the familiar hom…
102 <em>Home</em> or <em>Up</em>, make sure to clear the back stack of any descendent screens. For
103 <em>Home</em>, the only remaining screen on the back stack should be the home screen. For
[all …]
/frameworks/compile/mclinker/include/mcld/
DModule.h126 LDSection* back () { return m_SectionTable.back(); } in back() function
127 const LDSection* back () const { return m_SectionTable.back(); } in back() function
/frameworks/base/docs/html/training/animation/
Dcardflip.jd92 for when the back of the card animates in and from the right and out and to the right.
250 Create fragment classes for the front and back of the card. These classes return the layouts
271 * A fragment representing the back of the card.
324 Now that you have the front of the card showing, you can show the back of the card
334 <li>Adds the previously displayed fragment to the fragment back stack
335 so when the user presses the <em>Back</em> button, the card flips back over.
345 // Flip to the back.
349 // Create and commit a new fragment transaction that adds the fragment for the back of
350 // the card, uses custom animations, and is part of the fragment manager's back stack.
356 // rotations when switching to the back of the card, as well as animator
[all …]
/frameworks/base/docs/html/design/patterns/
Dfullscreen.jd18 back into view.
24 <p>Touch the screen anywhere to bring back system bars. </p>
29 <p>Swipe from the any edge of the screen with a hidden bar to bring back system bars. </p>
46 In this type of experience, users are leaning back and watching the screen.
47 Then, when they need to bring back the bars, they simply touch anywhere. This
65 In this type of experience, when users need to bring back the system bars,
79 The user learns about the gesture to bring back the system bars through a
/frameworks/compile/libbcc/bcinfo/BitReader_2_7/
DBitcodeReader.h76 Value *back() const { return ValuePtrs.back(); } in back() function
111 Value *back() const { return MDValuePtrs.back(); } in back() function
/frameworks/compile/libbcc/bcinfo/BitReader_3_0/
DBitcodeReader.h76 Value *back() const { return ValuePtrs.back(); } in back() function
111 Value *back() const { return MDValuePtrs.back(); } in back() function
/frameworks/base/docs/html/guide/components/
Dtasks-and-back-stack.jd24 <li><a href="#Clearing">Clearing the back stack</a></li>
64 when performing a certain job. The activities are arranged in a stack (the "back stack"), in the
70 <h3>Adding fragments to a task's back stack</h3>
72 <p>Your activity can also include {@link android.app.Fragment}s to the back stack. For example,
76 desireable for the user to navigate back to reveal fragment B, using the <em>Back</em> button.</p>
77 <p>In order to add fragment B to the back stack so that this is possible, you must call {@link
81 <p>For more information about using fragments and adding them to the back stack, see the {@link
102 the back
104 this behavior with a timeline showing the progress between activities along with the current back
109 task adds an item to the back stack. When the user presses the <em>Back</em> button, the current
[all …]
Dfragments.jd13 <li>Fragments have their own lifecycle, state, and back stack</li>
71 fragment transaction, you can also add it to a back stack that's managed by the
72 activity&mdash;each back stack entry in the activity is a record of the fragment transaction that
73 occurred. The back stack allows the user to reverse a fragment transaction (navigate backwards),
86 how fragments can maintain their state when added to the activity's back stack, share
98 to modify the activity's appearance at runtime and preserve those changes in a back stack
170 the user might not come back).</dd>
186 incorporate a fragment dialog into the back stack of fragments managed by the activity,
393 <li>Pop fragments off the back stack, with {@link
395 <li>Register a listener for changes to the back stack, with {@link
[all …]
/frameworks/base/docs/html/training/notify-user/
Dnavigation.jd94 Create a back stack based on the {@link android.content.Intent} that starts the
101 // Adds the back stack
105 // Gets a PendingIntent containing the entire back stack
119 A special {@link android.app.Activity} doesn't need a back stack, so you don't have to
123 back stack. Instead, use the manifest to set up the {@link android.app.Activity} task options,
154 navigate back to it.
/frameworks/base/docs/html/google/backup/
Dindex.jd24 Service does not guarantee that it will always back up data using this service
26 data backup in your application, then it will back up using whichever transport is enabled
27 on the device. Registering with Android Backup Service allows your application to back up
60 Backup Service Key are ignored&mdash;your application will work normally, but will either back up
/frameworks/compile/mclinker/lib/Object/
DObjectBuilder.cpp154 offset = pSD.back().getOffset() + pSD.back().size(); in AppendFragment()
/frameworks/base/docs/html/training/efficient-downloads/
Dregular_updates.jd19 …OptimizedPolling">Optimize polling with inexact repeating alarms and exponential back-offs</a></li>
69 <p>One approach is to implement an exponential back-off pattern to reduce the frequency of your upd…
89 <p>You can use a similar exponential back-off pattern to reduce the effect of failed connections an…
91 …sitive transfers where successful completion is important, an exponential back-off algorithm can b…
/frameworks/base/docs/html/training/basics/fragments/
Dfragment-ui.jd159 to the back stack, the fragment that is removed is stopped (not destroyed). If the user navigates
160 back to restore the fragment, it restarts. If you <em>do not</em> add the transaction to the back
175 // and add the transaction to the back stack so the user can navigate back
/frameworks/wilhelm/tools/hashgen/
DREADME.txt11 If the differences look OK, then copy the new IID_to_MPH.c back to
/frameworks/base/docs/html/guide/topics/data/
Dindex.jd17 data with the cloud using your own back-end web application, and backing up data using the cloud so

123456789