| /frameworks/base/docs/html/training/transitions/ |
| D | custom-transitions.jd | 23 child views of both the starting and ending scenes. Unlike built-in transition types,
61 animations change a view property between a starting and ending value over a specified
62 period of time, so the framework needs to have both the starting and ending value of
75 <p>To pass the starting view values to the framework, implement the
77 method. The framework calls this method for every view in the starting scene. The method
143 starting and ending scenes. The framework maintains separate maps for the starting and ending
150 <p>To animate the changes to a view between its state in the starting scene and its state in
154 android.transition.TransitionValues} objects that contain the starting and ending values
159 occur between the starting and ending scenes. For example, consider a fade out/fade in animation
160 implemented as a custom transition. If the starting scene has five targets of which two are
[all …]
|
| D | transitions.jd | 20 between the view hierarchies in the starting and ending scenes. The framework represents
33 different view hierarchies. Once you have defined the starting scene and the ending scene you
142 starting scene is the ending scene from the last transition. If there was no previous
143 transition, the starting scene is determined automatically from the current state of the
154 <p>The framework applies transitions to all views in the starting and ending scenes by
164 android.transition.Transition#removeTarget removeTarget()} method before starting
305 from the starting view hierarchy to the ending view hierarchy during a scene change. You
306 cannot simply copy the value from its starting view to the view in the ending view hierarchy,
|
| D | overview.jd | 30 <dd>Runs animations based on the changes between starting and ending view property values.</dd>
67 over time between the initial or <em>starting</em> view hierarchy and the final or <em>ending</em>
104 <p>In most cases, you do not create a starting scene explicitly. If you have applied a
105 transition, the framework uses the previous ending scene as the starting scene for any
124 between the view hierarchies in the starting and ending scenes. Information about the animation
|
| D | scenes.jd | 17 values. The transitions framework can run animations between a starting and an ending scene.
18 The starting scene is often determined automatically from the current state of the user
194 starting and ending scenes using exit and entry scene actions.</li>
203 calls the {@link android.transition.Scene#setExitAction setExitAction()} method on the starting
209 the starting and ending scenes. For more information, see
|
| /frameworks/base/services/core/java/com/android/server/am/ |
| D | LockTaskNotify.java | 69 public void show(boolean starting) { in show() argument
71 if (starting) { in show()
|
| D | CompatModePackages.java | 328 ActivityRecord starting = stack.restartPackage(packageName); in setPackageScreenCompatModeLocked() local
346 if (starting != null) { in setPackageScreenCompatModeLocked()
347 stack.ensureActivityConfigurationLocked(starting, 0); in setPackageScreenCompatModeLocked()
350 stack.ensureActivitiesVisibleLocked(starting, 0); in setPackageScreenCompatModeLocked()
|
| /frameworks/base/docs/html-intl/intl/ja/training/basics/activity-lifecycle/ |
| D | index.jd | 60 <dt><b><a href="starting.html">アクティビティを開始する</a></b></dt>
|
| /frameworks/base/docs/html-intl/intl/ru/training/basics/activity-lifecycle/ |
| D | index.jd | 60 <dt><b><a href="starting.html">Запуск операции</a></b></dt>
|
| /frameworks/base/docs/html-intl/intl/zh-tw/training/basics/activity-lifecycle/ |
| D | index.jd | 60 <dt><b><a href="starting.html">啟動應用行為顯示</a></b></dt>
|
| /frameworks/base/docs/html/samples/ |
| D | index.jd | 33 <strong>Note:</strong> When starting Android Studio, you can also select <strong>Import an
65 <strong>Note:</strong> When starting Android Studio, you can also select <strong>Import
|
| /frameworks/base/docs/html-intl/intl/ko/training/basics/activity-lifecycle/ |
| D | index.jd | 60 <dt><b><a href="starting.html">액티비티 시작하기</a></b></dt>
|
| /frameworks/base/docs/html-intl/intl/zh-cn/training/basics/activity-lifecycle/ |
| D | index.jd | 60 <dt><b><a href="starting.html">开始Activity</a></b></dt>
|
| /frameworks/base/docs/html/guide/topics/graphics/ |
| D | view-animation.jd | 30 set of parameters specific for that transformation (starting size and ending size for size
31 change, starting angle and ending angle for rotation, and so on), and also a set of common
103 <p>As an alternative to <code>startAnimation()</code>, you can define a starting time for the
|
| /frameworks/base/cmds/uiautomator/cmds/uiautomator/ |
| D | uiautomator | 29 # before starting the Java code. This offloads the task of class loading
82 # we are done with jars, starting with parameters now
|
| /frameworks/native/services/surfaceflinger/EventLog/ |
| D | EventLogTags.logtags | 12 # starting with '#' are ignored.
|
| /frameworks/base/docs/html/tools/help/ |
| D | MonkeyImage.jd | 214 The horizontal position of the pixel, starting with 0 at the left of the screen in the
221 The vertical position of the pixel, starting with 0 at the top of the screen in the
265 The horizontal position of the pixel, starting with 0 at the left of the screen in the
272 The vertical position of the pixel, starting with 0 at the top of the screen in the
|
| /frameworks/base/docs/html/tools/adk/ |
| D | index.jd | 6 hobbyists to use as a starting point for building accessories for Android. Each ADK release is
|
| /frameworks/base/docs/html/ndk/guides/ |
| D | x86-64.jd | 49 <p>The NDK provides native versions of Android APIs for 64-bit x86 machine code starting from
|
| /frameworks/base/docs/html/training/notepad/ |
| D | index.jd | 50 tutorial before starting this one.</p>
66 the starting points for each of the exercises, while the
|
| /frameworks/base/docs/html/training/wearables/apps/ |
| D | voice.jd | 155 when starting and <code>CompletedActionStatus</code> when stopping.</dd>
171 when starting and <code>CompletedActionStatus</code> when stopping</dd>
188 when starting and <code>CompletedActionStatus</code> when stopping</dd>
|
| /frameworks/base/docs/html/training/animation/ |
| D | zoom.jd | 176 <li>Calculate the starting and ending bounds for the {@link android.widget.ImageView}.
181 simultaneously, from the starting bounds to the ending bounds. These four animations are
205 // Calculate the starting and ending bounds for the zoomed-in image.
|
| /frameworks/base/docs/html/distribute/users/ |
| D | build-community.jd | 27 <h2 id="starting-your-community">
77 Any way you do it, starting your community early helps you build momentum as
|
| /frameworks/base/docs/html/tools/debugging/ |
| D | debugging-projects.jd | 22 Eclipse also takes care of starting the ADB host daemon for you, so you do not have to run this
|
| /frameworks/base/docs/html/training/load-data-background/ |
| D | index.jd | 59 versions of classes, which support platforms starting with Android 1.6.
|
| /frameworks/base/docs/html/training/basics/intents/ |
| D | result.jd | 41 {@link android.app.Activity#startActivityForResult startActivityForResult()}. When starting one of
48 <p>There's nothing special about the {@link android.content.Intent} object you use when starting
|