| /external/chromium_org/ui/views/focus/ |
| focus_manager.cc | 165 // Get the list of all accessible panes.
166 std::vector<View*> panes; local
167 widget_->widget_delegate()->GetAccessiblePanes(&panes);
169 // Count the number of panes and set the default index if no pane
171 int count = static_cast<int>(panes.size());
183 if (panes[i] && panes[i]->Contains(focused_view)) {
206 views::View* pane = panes[index];
|
| focus_manager_unittest.cc | 629 std::vector<views::View*> panes; local
630 panes.push_back(pane1);
631 panes.push_back(pane2);
632 SetAccessiblePanes(panes);
667 // panes, RotatePaneFocus should return false but the current
[all...] |
| focus_manager.h | 301 // no panes, the widget's root view is treated as a single pane.
|
| /external/chromium_org/ui/views/ |
| accessible_pane_view.h | 20 // F6 to traverse all panes, or by pressing a shortcut that jumps directly
|
| /external/lldb/utils/vim-lldb/doc/ |
| lldb.txt | 22 there are also commands to display or hide informational debugger panes.
|
| /external/chromium_org/chrome/common/extensions/docs/templates/articles/ |
| devtools.html | 88 <h2 id="devtools-ui">DevTools UI Elements: Panels and Sidebar Panes</h2>
100 Styles, Computed Styles, and Event Listeners panes on the Elements panel are
101 examples of sidebar panes. Currently your extension can only add sidebar panes to
102 the Elements panel. (Note that the appearance of sidebar panes may not match the
|
| /frameworks/base/docs/html/tools/debugging/ |
| debugging-ui.jd | 130 You should see four panes:
362 In it, you see three panes:
438 The panes are not automatically refreshed when you change one of the View objects or go to
440 <strong>Refresh Screenshot</strong> at the top of the window. This will change the panes
445 To automatically refresh the panes while you are debugging, set
|
| debugging-tracing.jd | 51 <p>The sections below provide addition information about the traceview output panes.</p>
|
| /prebuilts/python/darwin-x86/2.7.5/lib/python2.7/lib-tk/test/test_ttk/ |
| test_widgets.py | 376 self.assertEqual(self.paned.panes(), (str(child), str(child2)))
379 self.assertEqual(self.paned.panes(), (str(child2), str(child)))
382 self.assertEqual(self.paned.panes(),
386 panes = self.paned.panes()
388 self.assertEqual(panes, self.paned.panes())
394 self.assertEqual(self.paned.panes(),
[all...] |
| /prebuilts/python/linux-x86/2.7.5/lib/python2.7/lib-tk/test/test_ttk/ |
| test_widgets.py | 376 self.assertEqual(self.paned.panes(), (str(child), str(child2)))
379 self.assertEqual(self.paned.panes(), (str(child2), str(child)))
382 self.assertEqual(self.paned.panes(),
386 panes = self.paned.panes()
388 self.assertEqual(panes, self.paned.panes())
394 self.assertEqual(self.paned.panes(),
[all...] |
| /frameworks/base/docs/html/training/implementing-navigation/ |
| descendant.jd | 47 <p>Handset touchscreens are most suitable for displaying one screen at a time (either the master or the detail screen); this concern is further discussed in <a href="{@docRoot}training/design-navigation/multiple-sizes.html">Planning for Multiple Touchscreen Sizes</a>. Descendant navigation in this case is often implemented using an {@link android.content.Intent} that starts an activity representing the detail screen. On the other hand, tablet displays, especially when viewed in the landscape orientation, are best suited for showing multiple content panes at a time: the master on the left, and the detail to the right). Here, descendant navigation is usually implemented using a {@link android.app.FragmentTransaction} that adds, removes, or replaces the detail pane with new content.</p>
|
| /pdk/apps/TestingCamera2/src/com/android/testingcamera2/ |
| ControlPane.java | 182 * Called when other panes want to inform the rest of the app of interesting events
|
| /frameworks/support/v4/java/android/support/v4/widget/ |
| SlidingPaneLayout.java | 69 * a physicality and direct information hierarchy between panes that does not necessarily exist
72 * <p>Appropriate uses of SlidingPaneLayout include pairings of panes such as a contact list and
121 * Drawable used to draw the shadow between panes by default.
126 * Drawable used to draw the shadow between panes to support RTL (right to left language).
209 * Listener for monitoring events about sliding panes.
221 * @param panel The child view that was slid to an open position, revealing other panes
743 // Recalculate sliding panes and their details
[all...] |
| /external/qemu/android/camera/ |
| camera-format-converters.c | 358 * is divided into three separate panes that can be mixed together in any way
370 * there are three ways how color panes are arranged:
379 * containing interleaved U, and V panes.
404 * line in the U/V panes table is shared between two adjacent lines in Y pane,
504 * - For YUV format that use fully separated Y, U, and V panes this field
505 * defines order of U and V panes in the framebuffer:
706 * bytes. Eacht line in each of U and V panes contains width / 2 elements.
707 * Also, each line in each of U and V panes is shared between two Y lines.
[all...] |
| /external/chromium_org/remoting/host/setup/ |
| daemon_controller_delegate_mac.mm | 251 LOG(ERROR) << "Failed to get directory for local preference panes.";
|
| /external/chromium_org/ui/webui/resources/js/cr/ui/ |
| splitter.js | 7 * elements in split panes.
|
| /frameworks/support/v4/java/android/support/v4/view/ |
| ViewGroupCompat.java | 177 * such as scrolling two panes of content independently, chording of buttons, and performing
|
| /frameworks/base/docs/html/training/design-navigation/ |
| wireframing.jd | 39 <p>First, our second-level screens (<em>Story Category List</em>, <em>Photo List</em>, and <em>Saved Item List</em>) can be grouped together using tabs. Note that we don't necessarily have to use horizontally arranged tabs; in some cases a drop-down list UI element can serve as a suitable replacement, especially on devices with narrow screens such as handsets. We can also group the <em>Saved Photo List</em> and <em>Saved Story List</em> screens together using tabs on handsets, or use multiple vertical content panes on tablets.</p>
|
| /packages/apps/Dialer/src/com/android/dialer/widget/ |
| OverlappingPaneLayout.java | 42 * A custom layout that aligns its child views vertically as two panes, and allows for the bottom
176 * Callbacks for interacting with sliding panes.
188 * @param panel The child view that was slid to an open position, revealing other panes
622 // Recalculate sliding panes and their details
[all...] |
| /external/chromium_org/chrome/browser/ui/views/frame/ |
| browser_view.cc | [all...] |
| /frameworks/base/docs/html/training/multiscreen/ |
| screensizes.jd | 158 another pane). Tablets and TVs are large enough for both panes to fit
189 600 dp, so if you want your UI to have two panes on those screens (but a single
|
| /prebuilts/python/darwin-x86/2.7.5/lib/python2.7/lib-tk/ |
| Tix.py | 1263 def panes(self): member in class:PanedWindow
[all...] |
| /prebuilts/python/linux-x86/2.7.5/lib/python2.7/lib-tk/ |
| Tix.py | 1263 def panes(self): member in class:PanedWindow
[all...] |
| /external/chromium_org/chrome/browser/ui/views/ |
| collected_cookies_views.cc | 303 // NOTE: Panes must be added after |tabbed_pane| has been added to its parent.
|
| /packages/apps/Calendar/src/com/android/calendar/agenda/ |
| AgendaFragment.java | 192 // Since using weight for sizing the two panes of the agenda fragment causes the whole
|
