Home
last modified time | relevance | path

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

12345678910>>...12

/frameworks/compile/mclinker/include/mcld/Support/
DCXADemangle.tcc551 if (!db.template_param.back().empty()) in parse_template_param()
553 for (auto& t : db.template_param.back().front()) in parse_template_param()
576 if (sub < db.template_param.back().size()) in parse_template_param()
578 for (auto& temp : db.template_param.back()[sub]) in parse_template_param()
610 auto expr = db.names.back().move_full(); in parse_const_cast_expr()
612 db.names.back() = "const_cast<" + db.names.back().move_full() + ">(" + expr + ")"; in parse_const_cast_expr()
636 auto expr = db.names.back().move_full(); in parse_dynamic_cast_expr()
638 db.names.back() = "dynamic_cast<" + db.names.back().move_full() + ">(" + expr + ")"; in parse_dynamic_cast_expr()
662 auto expr = db.names.back().move_full(); in parse_reinterpret_cast_expr()
664 … db.names.back() = "reinterpret_cast<" + db.names.back().move_full() + ">(" + expr + ")"; in parse_reinterpret_cast_expr()
[all …]
/frameworks/compile/mclinker/include/mcld/Script/
DStringList.h48 const_reference back() const { return m_Tokens.back(); } in back() function
49 reference back() { return m_Tokens.back(); } in back() function
DSectionsCmd.h45 const_reference back() const { return m_SectionCommands.back(); } in back() function
46 reference back() { return m_SectionCommands.back(); } in back() function
DScriptFile.h63 const_reference back() const { return m_CommandQueue.back(); } in back() function
64 reference back() { return m_CommandQueue.back(); } in back() function
DOutputSectDesc.h176 const_reference back() const { return m_OutputSectCmds.back(); } in back() function
177 reference back() { return m_OutputSectCmds.back(); } in back() function
/frameworks/compile/mclinker/include/mcld/LD/
DELFSegmentFactory.h39 const ELFSegment* back() const { return m_Segments.back(); } in back() function
40 ELFSegment* back() { return m_Segments.back(); } in back() function
DSectionData.h69 reference back () { return m_Fragments.back(); } in back() function
70 const_reference back () const { return m_Fragments.back(); } in back() function
DRelocData.h79 reference back () { return m_Relocations.back(); } in back() function
80 const_reference back () const { return m_Relocations.back(); } in back() function
DELFSegment.h55 LDSection* back() { return m_SectionList.back(); } in back() function
56 const LDSection* back() const { return m_SectionList.back(); } in back() function
/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 …]
/frameworks/compile/mclinker/include/mcld/Object/
DSectionMap.h102 const_reference back () const { return m_InputList.back(); } in back() function
103 reference back () { return m_InputList.back(); } in back() function
184 const_reference back () const { return m_OutputDescList.back(); } in back() function
185 reference back () { return m_OutputDescList.back(); } in back() function
/frameworks/compile/mclinker/lib/Script/
DScriptFile.cpp92 SectionsCmd* sections = llvm::cast<SectionsCmd>(back()); in addEntryPoint()
145 SectionsCmd* sections = llvm::cast<SectionsCmd>(back()); in addAssignment()
149 llvm::cast<OutputSectDesc>(sections->back()); in addAssignment()
190 SectionsCmd* sections = llvm::cast<SectionsCmd>(back()); in enterOutputSectDesc()
200 SectionsCmd* sections = llvm::cast<SectionsCmd>(back()); in leaveOutputSectDesc()
203 OutputSectDesc* output_desc = llvm::cast<OutputSectDesc>(sections->back()); in leaveOutputSectDesc()
214 SectionsCmd* sections = llvm::cast<SectionsCmd>(back()); in addInputSectDesc()
217 OutputSectDesc* output_sect = llvm::cast<OutputSectDesc>(sections->back()); in addInputSectDesc()
DAssignment.cpp90 SectionMap::reference out = script.sectionMap().back(); in activate()
104 Assignment& prevDotAssign = out->dotAssignments().back(); in activate()
131 SectionMap::Output::reference in = script.sectionMap().back()->back(); in activate()
144 Assignment& prevDotAssign = in->dotAssignments().back().second; in activate()
/frameworks/compile/mclinker/lib/Target/Mips/
DMipsGOT.cpp123 it->m_pLastLocal = &m_SectionData->back(); in finalizeScanning()
125 it->m_pLastGlobal = &m_SectionData->back(); in finalizeScanning()
162 m_MultipartList.back().m_Inputs.insert(m_pInput); in initGOTList()
172 m_MultipartList.back().m_Inputs.insert(m_pInput); in changeInput()
192 m_MultipartList.back().m_LocalNum + in isGOTFull()
193 m_MultipartList.back().m_GlobalNum; in isGOTFull()
213 m_MultipartList.back().m_LocalNum -= m_InputLocalSymbols.size(); in split()
214 m_MultipartList.back().m_GlobalNum -= uniqueCount; in split()
215 m_MultipartList.back().m_Inputs.erase(m_pInput); in split()
219 m_MultipartList.back().m_Inputs.insert(m_pInput); in split()
[all …]
/frameworks/base/tools/layoutlib/bridge/src/com/android/layoutlib/bridge/bars/
DNavigationBar.java40 int back = 1; in NavigationBar() local
44 back = 3; in NavigationBar()
49 loadIcon(back, "ic_sysbar_back.png", density, isRtl); in NavigationBar()
/frameworks/base/docs/html/distribute/engage/
Dcommunity.jd2 …Building a community has many benefits, including improving your app and bringing users back to it.
15 bringing users back to them. Using social media, groups, and forum tools will
21 There are many tactics to bring users back to your apps. In addition to app
24 Any reason to go back to your app is a great post to share with your
Dapp-updates.jd2 page.metaDescription=Keeping your content fresh gives users a reason to come back.
9 Keeping your content fresh gives users a reason to come back. Use any
23 channels to remind users to come back.
/frameworks/base/docs/html/distribute/tools/promote/
Ddevice-art.jd193 landRes: ['shadow', 'back', 'fore'],
195 portRes: ['shadow', 'back', 'fore'],
206 landRes: ['shadow', 'back', 'fore'],
208 portRes: ['shadow', 'back', 'fore'],
220 landRes: ['shadow', 'back', 'fore'],
222 portRes: ['shadow', 'back', 'fore'],
234 landRes: ['shadow', 'back', 'fore'],
236 portRes: ['shadow', 'back', 'fore'],
248 landRes: ['shadow', 'back', 'fore'],
250 portRes: ['shadow', 'back', 'fore'],
[all …]
/frameworks/base/docs/html-intl/intl/zh-cn/distribute/tools/promote/
Ddevice-art.jd175 landRes: ['shadow', 'back', 'fore'],
177 portRes: ['shadow', 'back', 'fore'],
188 landRes: ['shadow', 'back', 'fore'],
190 portRes: ['shadow', 'back', 'fore'],
202 landRes: ['shadow', 'back', 'fore'],
204 portRes: ['shadow', 'back', 'fore'],
216 landRes: ['shadow', 'back', 'fore'],
218 portRes: ['shadow', 'back', 'fore'],
230 landRes: ['shadow', 'back', 'fore'],
232 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.h116 LDSection* back () { return m_SectionTable.back(); } in back() function
117 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.jd19 back into view.
25 <p>Touch the screen anywhere to bring back system bars. </p>
30 <p>Swipe from the any edge of the screen with a hidden bar to bring back system bars. </p>
47 In this type of experience, users are leaning back and watching the screen.
48 Then, when they need to bring back the bars, they simply touch anywhere. This
66 In this type of experience, when users need to bring back the system bars,
80 The user learns about the gesture to bring back the system bars through a
Dbuttons.jd19 back into view.
25 <p>Touch the screen anywhere to bring back system bars. </p>
30 <p>Swipe from the any edge of the screen with a hidden bar to bring back system bars. </p>
47 In this type of experience, users are leaning back and watching the screen.
48 Then, when they need to bring back the bars, they simply touch anywhere. This
66 In this type of experience, when users need to bring back the system bars,
80 The user learns about the gesture to bring back the system bars through a
/frameworks/base/docs/html/guide/components/
Dtasks-and-back-stack.jd16 <li><a href="#Clearing">Clearing the back stack</a></li>
58 when performing a certain job. The activities are arranged in a stack (the <em>back stack</em>), in
64 <h3>Adding fragments to a task's back stack</h3>
66 <p>Your activity can also include {@link android.app.Fragment}s to the back stack. For example,
70 desireable for the user to navigate back to reveal fragment B, using the <em>Back</em> button.</p>
71 <p>In order to add fragment B to the back stack so that this is possible, you must call {@link
75 <p>For more information about using fragments and adding them to the back stack, see the {@link
96 the back
98 this behavior with a timeline showing the progress between activities along with the current back
103 task adds an item to the back stack. When the user presses the <em>Back</em> button, the current
[all …]

12345678910>>...12