| /frameworks/base/core/java/android/transition/ |
| D | SidePropagation.java | 48 public void setSide(int side) { in setSide() argument
49 mSide = side; in setSide()
122 final int side; in distance() local
125 side = isRtl ? Gravity.RIGHT : Gravity.LEFT; in distance()
128 side = isRtl ? Gravity.LEFT : Gravity.RIGHT; in distance()
130 side = mSide; in distance()
133 switch (side) { in distance()
|
| /frameworks/base/docs/html/ndk/samples/ |
| D | sample_hellojni.jd | 11 <li><a href="#ji">Java-side Implementation</a></li>
12 <li><a href="#ci">C-side Implementation</a></li>
49 <h2 id="ji">Java-side Implementation</h2>
51 a function to retrieve a string from the native side, then displays it on the screen.</p>
65 side).</p>
78 <h2 id="ci">C-side Implementation</h2>
80 returns a string that <a href="#ji">the Java side requested</a>). The function declaration is as
115 the Java side.</p>
118 that is, the string that the function on the Java side had requested.</p>
|
| D | sample_teapot.jd | 11 <li><a href="#ji">Java-side Implementation</a></li>
12 <li><a href="#ni">Native-side Implementation</a></li>
75 <h2 id="ji">Java-side Implementation</h2>
79 block of code is most important from the perspective of the native-side implementation: The native
95 <h2 id="ni">Native-side Implementation</h2>
179 <p>Then, the following function calls back to the Java side to update the UI display.</p>
199 <p>Next, this function calls back to the Java side to draw a text box
200 superimposed on the screen rendered on the native side, and showing frame
|
| /frameworks/rs/java/tests/VrDemo/src/com/example/android/rs/vr/ |
| D | VrView.java | 281 public void cut(int side, float fractionx, float fractiony) { in cut() argument
283 f[side] += fractionx; in cut()
284 if (f[side] < 0) f[side] = 0; in cut()
285 if (f[side] > .8) f[side] = .8f; in cut()
286 f[side + 3] += fractiony; in cut()
287 if (f[side + 3] < 0) f[side + 3] = 0; in cut()
288 if (f[side + 3] > .8) f[side + 3] = .8f; in cut()
|
| /frameworks/base/docs/html/guide/topics/ui/controls/ |
| D | radiobutton.jd | 22 options side-by-side. If it's not necessary to show all options side-by-side, use a <a
|
| /frameworks/compile/libbcc/tests/debuginfo/ |
| D | lit.site.cfg | 19 # This file is common to both host and target side tests
74 # Tools that are specific to running host-side debugger integration tests:
81 # Tools that are specific to running target-side debugger integration tests:
|
| D | README | 19 The output is verified in the same way as host side tests, and the format
22 *** If you are running target-side tests, you must disable parallel
|
| /frameworks/compile/libbcc/tests/debuginfo/host-tests/ |
| D | lit.cfg | 19 ### Configuration file for target side debugger integration tests
60 # Apply host-side test macro substitutions
|
| /frameworks/compile/libbcc/tests/debuginfo/target-tests/ |
| D | lit.cfg | 19 ### Configuration file for target side debugger integration tests
85 # Apply target-side test macro substitutions
|
| /frameworks/av/media/libstagefright/codecs/on2/h264dec/omxdl/arm11/vc/m4p2/src/ |
| D | omxVCM4P2_DecodePadMV_PVOP_s.s | 44 ; * macroblocks specially at the left side of the current macroblock
47 ; * macroblocks specially at the upper side of the current macroblock
50 ; * macroblocks specially at the upper-right side of the current macroblock
|
| /frameworks/av/media/libstagefright/codecs/on2/h264dec/omxdl/arm_neon/vc/m4p2/src/ |
| D | omxVCM4P2_DecodePadMV_PVOP_s.s | 44 ; * macroblocks specially at the left side of the current macroblock
47 ; * macroblocks specially at the upper side of the current macroblock
50 ; * macroblocks specially at the upper-right side of the current macroblock
|
| /frameworks/base/docs/html/guide/practices/ui_guidelines/ |
| D | icon_design_launcher.jd | 151 alt="Side by side: overly complicated vs. simpler launcher icons"></td>
159 alt="Side by side: cropped and glossy vs. matte and single-shape launcher icons"></td>
168 alt="Side by side: overly thin vs. thicker, weightier icons"></td>
176 alt="Side by side: full-frame vs. subtly rounded and treated icons"></td>
238 launcher icon can contain a 88 x 88 pixel shape with 4 pixels on each side for padding.
|
| /frameworks/base/docs/html/sdk/installing/ |
| D | studio-layout.jd | 41 by opening the <strong>Preview</strong> pane available on the right side of the window.
89 particular theme and/or select one from the list on the right hand side. The theme you
119 left side of the window. Clicking <strong>Designer</strong> on the right side of the
|
| /frameworks/base/docs/html/training/basics/fragments/ |
| D | fragment-ui.jd | 41 for a single-pane user interface. Conversely, you may want to set fragments side-by-side on a
47 fit side by side, but on a handset device, only one fragment fits at a time so the fragments must
|
| /frameworks/base/docs/html/ndk/guides/ |
| D | setup.jd | 52 <li>In the pane on the left side of the <i>Preferences</i> window, select <i>Android</i>.
54 <li>Select <b>NDK</b>. In the pane on the right side of the <i>Preferences</i> window, browse to
|
| /frameworks/base/docs/html/training/animation/ |
| D | cardflip.jd | 201 Each side of the "card" is a separate layout that can contain any content you want,
204 create one side of a card that shows text:
236 and the other side of the card that displays an {@link android.widget.ImageView}:
326 side of the card that does the following things:
|
| /frameworks/base/libs/hwui/ |
| D | DeferredDisplayList.cpp | 157 static inline bool checkSide(const int currentFlags, const int newFlags, const int side, in checkSide() argument
159 bool currentClipExists = currentFlags & side; in checkSide()
160 bool newClipExists = newFlags & side; in checkSide()
|
| /frameworks/base/docs/html/training/wearables/data-layer/ |
| D | data-items.jd | 69 data item that allows you to access it from either side of the connection. The path must begin
129 <p>If one side of the data layer connection changes a data item, you probably want
130 to be notified of any changes on the other side of the connection.
|
| D | events.jd | 106 - Called when data item objects are created, changed, or deleted. An event on one side of a connect…
109 - A message sent from one side of a connection triggers this callback on the other side of the con…
113 Changes in connection state on one side of the connection trigger these callbacks on both sides
|
| /frameworks/base/docs/html/training/notify-user/ |
| D | display-progress.jd | 123 The resulting notifications are shown in figure 1. On the left side is a snapshot of the
124 notification during the operation; on the right side is a snapshot of it after the operation
|
| /frameworks/base/docs/html/design/patterns/ |
| D | compatibility.jd | 61 controls, an action overflow control appears at the right side of the virtual navigation bar. You
|
| /frameworks/base/docs/html/guide/webapps/ |
| D | webview.jd | 10 <li>You can create interfaces from your JavaScript to your client-side Android code</li>
64 client-side code in your Android application.</p>
143 application, you can create interfaces between your JavaScript code and client-side Android code.
221 your client-side code and possibly any code of the attacker's choosing. As such, you should not use
|
| /frameworks/base/docs/html/training/monitoring-device-state/ |
| D | manifest-receivers.jd | 35 <p>A side-effect of this approach is that your app will wake the device each time any of these
|
| /frameworks/rs/ |
| D | rsDefines.h | 453 RsBlasSide side; member
|
| /frameworks/base/docs/html/training/design-navigation/ |
| D | ancestral-temporal.jd | 99 … conversation list, as well as the conversation details are presented side-by-side. This is a form…
|