| /frameworks/support/v7/recyclerview/src/android/support/v7/widget/ |
| D | DefaultItemAnimator.java | 113 final ArrayList<MoveInfo> moves = new ArrayList<>(); in runPendingAnimations() local
114 moves.addAll(mPendingMoves); in runPendingAnimations()
115 mMovesList.add(moves); in runPendingAnimations()
120 for (MoveInfo moveInfo : moves) { in runPendingAnimations()
124 moves.clear(); in runPendingAnimations()
125 mMovesList.remove(moves); in runPendingAnimations()
129 View view = moves.get(0).holder.itemView; in runPendingAnimations()
460 ArrayList<MoveInfo> moves = mMovesList.get(i); in endAnimation() local
461 for (int j = moves.size() - 1; j >= 0; j--) { in endAnimation()
462 MoveInfo moveInfo = moves.get(j); in endAnimation()
[all …]
|
| /frameworks/base/docs/html/training/snackbar/ |
| D | showing.jd | 54 <li>The layout moves some other UI elements when the {@link
57 moves the button up when it shows a {@link
104 moves other elements up when it shows the Snackbar.">
112 moves the {@link android.support.design.widget.FloatingActionButton} up
|
| /frameworks/support/recommendation/ |
| D | build.gradle | 23 // this moves src/instrumentTest to tests so all folders follow:
|
| /frameworks/base/docs/html/training/keyboard-input/ |
| D | navigation.jd | 72 <p>Look for any instances in which the focus moves in a way you don't expect.</p>
77 <p>Look for any instances in which the focus moves in a way you don't expect.</p>
126 focus appropriately moves according to the appearance on the screen: from
|
| D | visibility.jd | 21 <p>When input focus moves into or out of an editable text field, Android shows
|
| /frameworks/support/v17/leanback/src/android/support/v17/leanback/widget/ |
| D | GridLayoutManager.java | 3296 private int processSelectionMoves(boolean preventScroll, int moves) { in processSelectionMoves() argument
3298 return moves; in processSelectionMoves()
3304 for (int i = 0, count = getChildCount(); i < count && moves != 0; i++) { in processSelectionMoves()
3305 int index = moves > 0 ? i : count - 1 - i; in processSelectionMoves()
3317 if ((moves > 0 && position > focusPosition) in processSelectionMoves()
3318 || (moves < 0 && position < focusPosition)) { in processSelectionMoves()
3321 if (moves > 0) { in processSelectionMoves()
3322 moves--; in processSelectionMoves()
3324 moves++; in processSelectionMoves()
3342 return moves; in processSelectionMoves()
|
| /frameworks/support/percent/ |
| D | build.gradle | 33 // this moves src/instrumentTest to tests so all folders follow:
|
| /frameworks/support/v7/gridlayout/ |
| D | build.gradle | 31 // this moves src/instrumentTest to tests so all folders follow:
|
| /frameworks/support/v14/preference/ |
| D | build.gradle | 40 // this moves src/instrumentTest to tests so all folders follow:
|
| /frameworks/support/v7/preference/ |
| D | build.gradle | 38 // this moves src/instrumentTest to tests so all folders follow:
|
| /frameworks/support/v17/preference-leanback/ |
| D | build.gradle | 42 // this moves src/instrumentTest to tests so all folders follow:
|
| /frameworks/support/v7/mediarouter/ |
| D | build.gradle | 25 // this moves src/instrumentTest to tests so all folders follow:
|
| /frameworks/base/docs/html/training/basics/activity-lifecycle/ |
| D | index.jd | 46 lifecycle methods on your activity as it moves into the background (where the activity is no
|
| D | starting.jd | 53 each callback method moves the activity state one step toward the top. The top of the pyramid is the
131 <p>The other states (Created and Started) are transient and the system quickly moves from them to
|
| /frameworks/base/docs/html/training/load-data-background/ |
| D | handle-results.jd | 55 {@link android.support.v4.widget.CursorAdapter}. The system then automatically moves data from
|
| /frameworks/base/docs/html/training/gestures/ |
| D | movement.jd | 81 <li>The velocity of the pointer as it moves across the touch screen.</li>
|
| D | scale.jd | 91 position of the active pointer, calculates the distance the pointer traveled, and moves the object …
|
| /frameworks/base/docs/html/training/volley/ |
| D | simple.jd | 95 {@code add()}, as shown above. Once you add the request it moves through the pipeline,
|
| /frameworks/base/docs/html/guide/topics/graphics/ |
| D | prop-animation.jd | 95 to travel is 40 pixels. Every 10 ms, which is the default frame refresh rate, the object moves
98 object moves at a constant speed.</p><img src="{@docRoot}images/animation/animation-linear.png">
104 end of the animation. The object still moves 40 pixels in 40 ms, but non-linearly. In the
304 animation, meaning the animation moves evenly the entire time, or you can specify animations
698 meaning the animation moves evenly the entire time, or you can specify animations to use
|
| /frameworks/base/docs/html/training/articles/ |
| D | perf-anr.jd | 187 <li>For games specifically, do calculations for moves in a worker
|
| /frameworks/base/docs/html/about/dashboards/ |
| D | index.jd | 458 // moves that src value into a real src attribute at runtime. This should be
|
| /frameworks/base/docs/html/wear/ |
| D | index.jd | 45 <div class="landing-subhead hero">Information that moves with you.</div>
|
| /frameworks/base/docs/html/training/custom-views/ |
| D | making-interactive.jd | 145 …user quickly moves a finger across the screen and then lifts it. This gesture makes sense if the UI
|
| /frameworks/base/docs/html/design/patterns/ |
| D | actionbar.jd | 137 estate, the system shows your most important actions as action buttons and moves the rest to the
|
| /frameworks/base/docs/html/guide/topics/sensors/ |
| D | sensors_motion.jd | 300 <li>If you push the device on the left side (so it moves to the right), the x acceleration value
302 <li>If you push the device on the bottom (so it moves away from you), the y acceleration value is
|