| /external/autotest/server/site_tests/autoupdate_EndToEndTest/ |
| update_engine_performance_monitor.py | 54 bytes. The task and its siblings (e.g. tasks belonging to the
|
| /external/avahi/avahi-core/ |
| prioq.c | 206 /* Swap siblings */
|
| /external/libxml2/doc/ |
| tree.html | 16 chained in double-linked lists of siblings and with a children<->parent
|
| /external/skia/src/xml/ |
| SkDOM.cpp | 234 else // this adds siblings in reverse order. gets corrected in onEndElement()
|
| /frameworks/base/core/java/android/view/ |
| ViewStructure.java | 62 * to the physical Z-ordering of this view relative to its other siblings (that is how
|
| /frameworks/base/docs/html/training/improving-layouts/ |
| optimizing-layout.jd | 144 <li>Useless parent - A layout with children that has no siblings, is not a {@link android.widget.ScrollView} or a root layout, and does not have a background, can be removed and have its children moved directly into the parent for a flatter and more efficient layout hierarchy.</li>
|
| /sdk/eclipse/plugins/com.android.ide.eclipse.adt/src/com/android/ide/eclipse/adt/internal/assetstudio/ |
| CreateAssetSetWizard.java | 222 // some siblings of the real files. I've tried a number of workarounds:
|
| /sdk/eclipse/plugins/com.android.ide.eclipse.adt/src/com/android/ide/eclipse/adt/internal/editors/manifest/pages/ |
| ApplicationToggle.java | 283 // The returned node looses its parents/siblings pointers.
|
| /external/valgrind/exp-bbv/tests/amd64-linux/ |
| ll.S | 578 .ascii "siblings : 2\n"
603 .ascii "siblings : 2\n"
|
| /packages/apps/Launcher2/src/com/android/launcher2/ |
| FocusHelper.java | 153 // child siblings willy-nilly
311 // Side pages do not always load synchronously, so check before focusing child siblings
[all...] |
| /sdk/eclipse/plugins/com.android.ide.eclipse.adt/src/com/android/ide/eclipse/adt/internal/editors/layout/gle2/ |
| ViewHierarchy.java | 494 // Iterate in REVERSE z order such that siblings on top
495 // are checked before earlier siblings (this matters in layouts like
|
| SelectionManager.java | 670 /** Selects the siblings of the primary */
[all...] |
| ClipboardSupport.java | 210 // Segment the deleted nodes into clusters of siblings
|
| /external/chromium-trace/catapult/third_party/beautifulsoup4/bs4/ |
| element.py | 353 # are siblings.
372 # are siblings.
401 """Returns the siblings of this Tag that match the given
433 """Returns the siblings of this Tag that match the given
[all...] |
| /external/chromium-trace/catapult/third_party/beautifulsoup4/doc/source/ |
| index.rst | 825 children of the same tag. We call them `siblings`. When a document is
826 pretty-printed, siblings show up at the same indentation level. You
851 The strings "text1" and "text2" are `not` siblings, because they don't
889 You can iterate over a tag's siblings with ``.next_siblings`` or
[all...] |
| /external/antlr/antlr-3.4/tool/src/main/java/org/antlr/tool/ |
| GrammarAST.java | 475 * duplicate that node and what's below; ignore siblings of root node.
|
| /external/apache-xml/src/main/java/org/apache/xalan/templates/ |
| ElemNumber.java | 220 * one plus the number of preceding siblings of that ancestor that match the count
224 * Preceding siblings has the same meaning here as with the preceding-sibling axis.
229 * one plus the number of preceding siblings of that node that match the count pattern.
232 * Preceding siblings has the same meaning here as with the preceding-sibling axis.
[all...] |
| /external/chromium-trace/catapult/third_party/html5lib-python/html5lib/treebuilders/ |
| etree_lxml.py | 6 Text or comments as siblings of the root element
|
| /external/llvm/test/CodeGen/WinEH/ |
| wineh-cloning.ll | 95 ; the two regions here are siblings, not parent-child).
|
| /external/skia/src/views/ |
| SkView.cpp | 505 if (fNextSibling != this) { // do we have any siblings
|
| /external/slf4j/slf4j-api/src/main/java/org/slf4j/helpers/ |
| MessageFormatter.java | 317 // allow repeats in siblings
|
| /frameworks/base/docs/html/training/design-navigation/ |
| descendant-lateral.jd | 169 <p>Additionally, for sibling-related screens, horizontal paging is most appropriate where there is some similarity in content type and when the number of siblings is relatively small. In these cases, this pattern can be used along with tabs above the content region to maximize the interface's intuitiveness. For collection-related screens, horizontal paging is most intuitive when there is a natural ordered relationship between screens, for example if each page represents consecutive calendar days. For infinite collections (again, calendar days), especially those with content in both directions, this paging mechanism can work quite well.</p>
|
| /external/autotest/client/site_tests/security_SeccompSyscallFilters/src/ |
| seccomp_bpf_tests.c | [all...] |
| /external/libgdx/gdx/src/com/badlogic/gdx/scenes/scene2d/ |
| Actor.java | 668 /** Changes the z-order for this actor so it is in front of all siblings. */
673 /** Changes the z-order for this actor so it is in back of all siblings. */
|
| /external/libxml2/ |
| runsuite.c | 482 * now scan all the siblings of correct to process the <valid> tests
542 * now scan all the siblings of correct to process the <invalid> tests
|
