From 3b9f0aa058e95fa0c998f787a8f4f7225e9850c0 Mon Sep 17 00:00:00 2001 From: kmccormick Date: Mon, 1 Apr 2013 18:08:28 -0700 Subject: [PATCH] Doc update: Misc doc bugs "Bug: 6515524" Change-Id: I1c8334e22637e9b55377a8743178bd5aa34ee9cd --- docs/html/guide/components/fragments.jd | 2 +- docs/html/guide/topics/graphics/prop-animation.jd | 4 ++-- .../guide/topics/resources/accessing-resources.jd | 12 +++++++----- .../guide/topics/resources/providing-resources.jd | 2 +- docs/html/guide/topics/search/search-dialog.jd | 1 + docs/html/guide/topics/ui/actionbar.jd | 2 +- docs/html/tools/debugging/ddms.jd | 2 +- docs/html/tools/device.jd | 2 +- docs/html/tools/projects/index.jd | 10 +++++----- docs/html/tools/testing/testing_android.jd | 4 ++-- docs/html/tools/workflow/index.jd | 2 +- 11 files changed, 23 insertions(+), 20 deletions(-) diff --git a/docs/html/guide/components/fragments.jd b/docs/html/guide/components/fragments.jd index 7747b3177fed0..32c9f99628580 100644 --- a/docs/html/guide/components/fragments.jd +++ b/docs/html/guide/components/fragments.jd @@ -172,7 +172,7 @@ the user might not come back).

Most applications should implement at least these three methods for every fragment, but there are several other callback methods you should also use to handle various stages of the -fragment lifecycle. All the lifecycle callback methods are discussed more later, in the section +fragment lifecycle. All the lifecycle callback methods are discussed in more detail in the section about Handling the Fragment Lifecycle.

diff --git a/docs/html/guide/topics/graphics/prop-animation.jd b/docs/html/guide/topics/graphics/prop-animation.jd index b733624a87273..49d7bb8732d29 100644 --- a/docs/html/guide/topics/graphics/prop-animation.jd +++ b/docs/html/guide/topics/graphics/prop-animation.jd @@ -479,7 +479,7 @@ ObjectAnimator.ofFloat(targetObject, "propName", 1f)
  • Depending on what property or object you are animating, you might need to call the {@link - android.view.View#invalidate invalidate()} method on a View force the screen to redraw itself with the + android.view.View#invalidate invalidate()} method on a View to force the screen to redraw itself with the updated animated values. You do this in the {@link android.animation.ValueAnimator.AnimatorUpdateListener#onAnimationUpdate onAnimationUpdate()} callback. For example, animating the color property of a Drawable object only cause updates to the @@ -825,7 +825,7 @@ rotationAnim.setDuration(5000ms);

    Animating Views

    -

    The property animation system allow streamlined animation of View objects and offerse +

    The property animation system allow streamlined animation of View objects and offers a few advantages over the view animation system. The view animation system transformed View objects by changing the way that they were drawn. This was handled in the container of each View, because the View itself had no properties to manipulate. diff --git a/docs/html/guide/topics/resources/accessing-resources.jd b/docs/html/guide/topics/resources/accessing-resources.jd index 0673b6fc75daa..8f99653f751b8 100644 --- a/docs/html/guide/topics/resources/accessing-resources.jd +++ b/docs/html/guide/topics/resources/accessing-resources.jd @@ -50,7 +50,7 @@ the {@code aapt} tool automatically generates.

    When your application is compiled, {@code aapt} generates the {@code R} class, which contains resource IDs for all the resources in your {@code res/} directory. For each type of resource, there is an {@code R} subclass (for example, -{@code R.drawable} for all drawable resources) and for each resource of that type, there is a static +{@code R.drawable} for all drawable resources), and for each resource of that type, there is a static integer (for example, {@code R.drawable.icon}). This integer is the resource ID that you can use to retrieve your resource.

    @@ -68,7 +68,7 @@ resource is a simple value (such as a string).

    • There are two ways you can access a resource: