When is View.onMeasure() called?

29,305

Solution 1

onMeasure is called when the parent View needs to calculate the layout. Typically, onMeasure may be called several times depending on the different children present and their layout parameters.

The best way to do something when onMeasure is called is (I think) to create your own control, extend the ImageView and override onMeasure (just call super.onMeasure and do whatever else you would like to do).

If you do that, just keep in mind that on Measure may be called several times with different parameters, so whatever is measured may not be the final width and height of what will be actually displayed.

Solution 2

You can get your custom view's measurements in onSizeChanged.

@Override
protected void onSizeChanged(int w, int h, int oldw, int oldh) {
    super.onSizeChanged(w, h, oldw, oldh);

    // use the provided width and height for whatever you need
}

Explanation

When a view is created, this is the order in which the following methods are called:

  1. Constructor
    • CustomView(Context context) (if created programmatically)
    • CustomView(Context context, AttributeSet attrs) (if created from xml)
  2. onFinishInflate (assuming you used the xml constructor)
  3. onAttachedToWindow
  4. onMeasure
  5. onSizeChanged
  6. onLayout
  7. onDraw

The earliest you can get the view's measurements is in onMeasure. Before that the width and height are 0. However, the only thing you should be doing in onMeasure is determining the size of the view. This method gets called several times while the view is telling the parent how big it wants to be but the parent is determining the actual final size. (See this answer for how onMeasure is meant to be used.)

If you want to actually use the measured size for anything, the earliest place to do that is in onSizeChanged. It gets called whenever the view is created because the size is changing from 0 to whatever the size is.

You could also use onLayout, though as I understand it, onLayout is for customizing how any children of your custom view are laid out. It also might get called more often than onSizeChanged, for example, if you call requestLayout() when the size hasn't actually changed.

You can also access the size in onDraw with getMeasuredWidth() and getMeasuredHeight(). However, if you are using them to do any heavy calculations, it is better to do that beforehand. Generally speaking, try to keep as much out of onDraw as possible since it may be called multiple times. (It gets called whenever invalidate() gets called.)

See for yourself

If you don't believe me, you can see the order of events as they are called in the custom view below. Here is the output:

XML constructor called, measured size: (0, 0)
onFinishInflate called, measured size: (0, 0)
onAttachedToWindow called, measured size: (0, 0)
onMeasure called, measured size: (350, 1859)
onMeasure called, measured size: (350, 350)
onMeasure called, measured size: (350, 2112)
onMeasure called, measured size: (350, 350)
onSizeChanged called, measured size: (350, 350)
onLayout called, measured size: (350, 350)
onDraw called, measured size: (350, 350)

activity_main.xml

<?xml version="1.0" encoding="utf-8"?>
<RelativeLayout
    xmlns:android="http://schemas.android.com/apk/res/android"
    android:id="@+id/activity_main"
    android:layout_width="match_parent"
    android:layout_height="match_parent">

    <com.example.viewlifecycle.CustomView
        android:id="@+id/customView"
        android:layout_width="100dp"
        android:layout_height="100dp"
        android:background="@color/colorAccent"/>

</RelativeLayout>

CustomView.java

public class CustomView extends View {

    private void printLogInfo(String methodName) {
        Log.i("TAG", methodName + " called, measured size: (" + getMeasuredWidth() + ", " + getMeasuredHeight() + ")");
    }

    // constructors

    public CustomView(Context context) {
        super(context);
        printLogInfo("Programmatic constructor");
    }

    public CustomView(Context context, AttributeSet attrs) {
        super(context, attrs);
        printLogInfo("XML constructor");
    }

    // lifecycle methods

    @Override
    protected void onFinishInflate() {
        super.onFinishInflate();
        printLogInfo("onFinishInflate");
    }

    @Override
    protected void onAttachedToWindow() {
        super.onAttachedToWindow();
        printLogInfo("onAttachedToWindow");
    }

    @Override
    protected void onMeasure(int widthMeasureSpec, int heightMeasureSpec) {
        super.onMeasure(widthMeasureSpec, heightMeasureSpec);
        printLogInfo("onMeasure");
    }

    @Override
    protected void onSizeChanged(int w, int h, int oldw, int oldh) {
        super.onSizeChanged(w, h, oldw, oldh);
        printLogInfo("onSizeChanged");
    }

    @Override
    protected void onLayout(boolean changed, int left, int top, int right, int bottom) {
        super.onLayout(changed, left, top, right, bottom);
        printLogInfo("onLayout");
    }

    @Override
    protected void onDraw(Canvas canvas) {
        super.onDraw(canvas);
        printLogInfo("onDraw");
    }
}

Further reading

Share:
29,305
GregNash
Author by

GregNash

I work in the Oil &amp; Gas industry for a company called Ion. I have been with Ion's Operations group since the first quarter of 2013. Working with Curt Schneider's Geophysical Support group, I report directly to Dave Flengte. Dave and I handle the majority of the Survey Design work that is done by Geophysical Support. With the addition of OceanGeo to the Ion family, my experience with designing land-based surveys has enabled me to support this group by designing surveys for their OBC (Ocean-bottom Cable) system. Informally reporting to Pete Stewart for this work, I provide a critical service that enables OceanGeo to be successfully awarded new seismic contracts.

Updated on March 21, 2020

Comments

  • GregNash
    GregNash about 4 years

    When is

    View.onMeasure(int widthMeasureSpec, int heightMeasureSpec)
    

    called? I have an Activity that needs to perform an action after onMeasure has been called.

    My question is the same as the unanswered question posted here. The View documentation states that onMeasure is called when requestLayout() is called, which is apparently called by a view on itself when it believes that is can no longer fit within its current bounds.

    However, this doesn't tell me when my activity can assume that my View has been measured. I've used this code to extend ImageView to form TouchImageView. It was suggested here that I should use the onMeasure method to scale my image. I wish to update the value of a TextView after the ImageView has been measured in order to display the percentage by which the image has been scaled.