| /frameworks/compile/mclinker/lib/CodeGen/ |
| D | MCLinker.cpp | 262 std::vector<InputAction*> actions; in initializeInputTree() local
263 actions.reserve(num_actions); in initializeInputTree()
271 actions.push_back(new InputFileAction(pos, *input)); in initializeInputTree()
272 actions.push_back(new ContextAction(pos)); in initializeInputTree()
273 actions.push_back(new MemoryAreaAction(pos, FileHandle::ReadOnly)); in initializeInputTree()
282 actions.push_back(new NamespecAction(pos, *namespec, in initializeInputTree()
284 actions.push_back(new ContextAction(pos)); in initializeInputTree()
285 actions.push_back(new MemoryAreaAction(pos, FileHandle::ReadOnly)); in initializeInputTree()
295 actions.push_back(new WholeArchiveAction(pos)); in initializeInputTree()
303 actions.push_back(new NoWholeArchiveAction(pos)); in initializeInputTree()
[all …]
|
| /frameworks/base/docs/html/design/patterns/ |
| D | selection.jd | 13 handle multi-select and contextual actions in your apps.</p>
22 actions for a given data item in a contextual menu.</p>
24 contextual actions and selection management functions for selected data into a new element called
69 <h4>Selecting CAB actions</h4>
70 <p>You can decide which actions and elements appear in the CAB. Use the guidelines in the <a href="…
73 <h4>Dynamically adjust CAB actions</h4>
74 <p>In most cases you need to adjust the actions in the CAB dynamically as the user adds more items …
83 Adjusting actions in the CAB as additional items are selected.
111 <p>Plan the actions you want to display inside of a CAB in the same way you would plan the actions
|
| D | actionbar.jd | 18 …<li>Makes important actions prominent and accessible in a predictable way (such as <em>New</em> or…
20 <li>Reduces clutter by providing an action overflow for rarely used actions.</li>
72 Show the most important actions of your app in the actions section. Actions that don't fit in the
80 Move less often used actions to the action overflow.
116 <p>To display actions and, if necessary, the action overflow, use the bottom bar.</p>
129 estate, the system shows your most important actions as action buttons and moves the rest to the
130 action overflow. The action bar should show only those actions that are available to the user. If a…
137 <p>For guidance on prioritizing actions, use the FIT scheme.</p>
175 Pre-defined glyphs should be used for certain common actions such as "refresh" and "share." The
193 <p>The action overflow in the action bar provides access to your app's less frequently used actions.
[all …]
|
| D | compatibility.jd | 26 <p>Android apps written for Android 3.0 and later display actions in the action bar. Actions that d…
45 resulting actions popup has the same style as in the previous example, but is displayed at the bott…
61 can touch the control to display the app's actions in the traditional Android menu styling.</p>
|
| D | notifications.jd | 16 …<li>Notifications can include actions that enable the user to immediately act on a notification fr…
51 … Jelly Bean, Android supports optional actions that are displayed at the bottom of the notificatio…
52 …actions you include with a notification. The more actions you include, the more cognitive complexi…
53 <p>Good candidates for actions on notifications are actions that are:</p>
57 <li>not overlapping with neighboring actions</li>
59 <p>Avoid actions that are:</p>
68 Calendar reminder notification with two actions
73 …actions, each consisting of an action icon and an action name. Adding actions to a simple base lay…
|
| D | app-structure.jd | 93 <h4>Set up action bars for navigation and actions</h4>
99 important actions.</p>
246 invocation of actions for a data item from within list or grid views, display prominent actions
247 directly on list view items using drop-downs or split list items. This lets people invoke actions on
260 delete multiple items in the category view. Analyze which detail view actions are applicable to
261 collections of items. Then use multi-select to allow application of those actions to multiple items
297 … screen without distractions. But that doesn't mean you can't also offer actions on the content li…
|
| D | new.jd | 84 …. It provides consistent navigation across the platform and allows your app to surface actions.</p>
109 …ow contextual actions for objects is now used for data selection. When selecting data, contextual …
|
| D | navigation-drawer.jd | 25 bar title with the app name and removing all actions that are contextual to the view underneath
184 <li>Remove actions from the action bar that are contextual to the underlying view (such as
185 Create new, Refresh). You may retain actions with global scope, such as “Search”.</li>
191 Clean up the action bar when the drawer is fully expanded. Remove actions that are not needed
200 Keep actions on the right side of the action bar and in the overflow
204 <p> Don’t place actions in the navigation drawer. Actions belong in the action bar, and the
207 but keep the bigger picture in mind. Place your actions where all apps display them.</p>
|
| /frameworks/compile/mclinker/unittests/ |
| D | InputTreeTest.cpp | 65 std::vector<InputAction*> actions; in TEST_F() local
68 actions.push_back(new StartGroupAction(position++)); in TEST_F()
69 actions.push_back(new InputFileAction(position++, "path1")); in TEST_F()
70 actions.push_back(new EndGroupAction(position++)); in TEST_F()
73 for (action = actions.begin(); action != actions.end(); ++action) { in TEST_F()
|
| /frameworks/base/core/java/android/app/ |
| D | Notification.java | 536 public Action[] actions; field in Notification
632 actions = parcel.createTypedArray(Action.CREATOR); // may be null in Notification()
711 if (this.actions != null) { in cloneInto()
712 that.actions = new Action[this.actions.length]; in cloneInto()
713 for(int i=0; i<this.actions.length; i++) { in cloneInto()
714 that.actions[i] = this.actions[i].clone(); in cloneInto()
839 parcel.writeTypedArray(actions, 0); // null ok in writeToParcel()
965 if (actions != null) { in toString()
967 sb.append(actions.length); in toString()
969 if (actions.length > 1) sb.append("s"); in toString()
[all …]
|
| /frameworks/base/docs/html/guide/topics/manifest/ |
| D | action-element.jd | 27 <dd>The name of the action. Some standard actions are defined in the
29 {@code ACTION_<i>string</i>} constants. To assign one of these actions to
36 For actions you define, it's best to use the package name as a prefix to
|
| /frameworks/base/docs/html/design/building-blocks/ |
| D | dialogs.jd | 36 …actions such as Close or Wait rather than a confirmation or cancellation of the action described i…
39 …<li>The dismissive action of a dialog is always on the left. Dismissive actions return to the user…
40 …<li>The affirmative actions are on the right. Affirmative actions continue progress toward the use…
|
| /frameworks/base/core/java/android/webkit/ |
| D | AccessibilityInjectorFallback.java | 501 int[] actions = new int[actionStrings.length]; in ensureWebContentKeyBindings() local
502 for (int i = 0, count = actions.length; i < count; i++) { in ensureWebContentKeyBindings()
503 actions[i] = Integer.decode(actionStrings[i].trim()); in ensureWebContentKeyBindings()
505 sBindings.add(new AccessibilityWebContentKeyBinding(keyCodeAndModifiers, actions)); in ensureWebContentKeyBindings()
|
| /frameworks/base/core/tests/bluetoothtests/src/android/bluetooth/ |
| D | BluetoothTestUtils.java | 1377 private void addReceiver(BroadcastReceiver receiver, String[] actions) { in addReceiver() argument
1379 for (String action: actions) { in addReceiver()
1387 String[] actions = { in getBluetoothReceiver() local
1393 addReceiver(receiver, actions); in getBluetoothReceiver()
1399 String[] actions = { in getPairReceiver() local
1403 addReceiver(receiver, actions); in getPairReceiver()
1409 String[] actions = { in getConnectProfileReceiver() local
1415 addReceiver(receiver, actions); in getConnectProfileReceiver()
1421 String[] actions = {BluetoothPan.ACTION_CONNECTION_STATE_CHANGED}; in getConnectPanReceiver() local
1423 addReceiver(receiver, actions); in getConnectPanReceiver()
[all …]
|
| /frameworks/base/docs/html/guide/topics/ui/ |
| D | menus.jd | 61 actions and other options in your activities.</p>
66 user actions.</p>
69 a set of actions and options is still based on the {@link android.view.Menu} APIs. This
76 activity. It's where you should place actions that have a global impact on the app, such as
84 don't have one), so you should migrate toward using the action bar to provide access to actions and
92 user performs a long-click on an element. It provides actions that affect the selected content or
95 href="#CAB">contextual action mode</a> to enable actions on selected content. This mode displays
103 invoked the menu. It's good for providing an overflow of actions that relate to specific content or
105 <strong>not</strong> directly affect the corresponding content—that's what contextual actions
106 are for. Rather, the popup menu is for extended actions that relate to regions of content in your
[all …]
|
| /frameworks/base/docs/html/design/get-started/ |
| D | ui-overview.jd | 104 <p>Notifications can be expanded to uncover more details and relevant actions. When collapsed, noti…
127 navigating your app's hierarchy and views, and also surfaces the most important actions.</p>
141 <p>Split action bars provide a way to distribute actions across additional bars located below
143 important actions that won't fit in the main bar to the bottom.</p>
|
| /frameworks/base/docs/html/guide/topics/ui/accessibility/ |
| D | services.jd | 23 <li><a href="#using-actions">Using accessibility actions</a></li>
300 user actions). If your service requires all views, it can request them by setting the
312 In Android 4.1 (API Level 16) the range of actions has been expanded to include scrolling lists
314 also take global actions, such as navigating to the Home screen, pressing the Back button, opening
351 and can respond by taking actions for the user.</p>
354 <h3 id="using-actions">Using accessibility actions</h3>
357 simpler and more productive. The ability of accessibility services to perform actions was added
360 <p>In order to take actions on behalf of users, your accessibility service must
424 applications that expect input focus to be in a specific location when certain actions are taken.
|
| /frameworks/base/docs/html/tools/help/ |
| D | adt.jd | 254 context-sensitive actions in the layout actions bar, such as adjusting layout margins and
256 The layout actions bar displays available actions depending on the selected UI element in the
292 <a href="http://www.youtube.com/watch?v=Oq05KqjXTvs#t=11m43s">layout actions bar</a>
354 … <li>Edit views with the layout actions bar: The context-sensitive layout actions bar allows you to
355 edit how a view is laid out in your UI. The available actions depend on the currently
356 selected view and its parent layout. Some common actions include
359 in a {@link android.widget.LinearLayout}, you see actions related to the {@link
362 aligned along their text baseline. You will also see toolbar actions to control the individual
|
| D | android.jd | 48 <h3>AVD actions and options</h3>
184 <h3>Project actions and options</h3>
411 <h3>Update actions</h3>
|
| /frameworks/base/docs/html/google/play-services/ |
| D | plus.jd | 47 to take specific actions in your app from a Google+ post, like "listen," "RSVP," "check-in,"
48 and over 100 more actions. <br />
|
| /frameworks/base/docs/html/training/notify-user/ |
| D | build-notification.jd | 57 <p>When creating a notification, specify the UI content and actions with a
88 <p>Although actions are optional, you should add at least one action to your
|
| /frameworks/base/docs/html/training/keyboard-input/ |
| D | index.jd | 52 <dd>Learn how to respond directly to keyboard input for user actions.
|
| /frameworks/base/docs/html/guide/practices/app-design/ |
| D | index.jd | 8 … by how well the application responds to the user's keypresses and other actions, how it well it i…
|
| /frameworks/base/docs/html/design/style/ |
| D | iconography.jd | 98 Action bar icons are graphic buttons that represent the most important actions people can take
105 Pre-defined glyphs should be used for certain common actions such as "refresh" and "share." The
193 <p>Within the body of your app, use small icons to surface actions and/or provide status for specif…
|
| D | touch-feedback.jd | 9 indicate what actions are enabled and disabled.</p>
|