Lines Matching defs:onMeasure

2950     protected void onMeasure(int widthSpec, int heightSpec) {
2960 mLayout.onMeasure(mRecycler, mState, widthSpec, heightSpec);
2989 mLayout.onMeasure(mRecycler, mState, widthSpec, heightSpec);
2992 // custom onMeasure
3016 mLayout.onMeasure(mRecycler, mState, widthSpec, heightSpec);
3023 * Used when onMeasure is called before layout manager is set
3185 * Called in onMeasure and dispatchLayout.
3261 // First 2 steps are done in onMeasure but looks like we have to run again due to
6847 * onMeasure method OR fake measure specs created by the RecyclerView.
6919 * @param widthSpec The widthSpec that was passing into RecyclerView's onMeasure
6920 * @param heightSpec The heightSpec that was passing into RecyclerView's onMeasure
6956 * measurement specs that were passed into {@link RecyclerView#onMeasure(int, int)}. It is
7047 * {@link LayoutManager#onMeasure(int, int)} to implement your custom measurement logic.
7052 * {@link RecyclerView#onMeasure(int, int)} call, then calculating desired dimensions based
7060 * <li>When {@link RecyclerView#onMeasure(int, int)} is called, if the provided specs are
7061 * exact, RecyclerView will only call LayoutManager's {@code onMeasure} and return without
7064 * layout process in {@code onMeasure} call. It will process all pending Adapter updates and
8066 * @see View#onMeasure(int, int)
8084 * @see View#onMeasure(int, int)
9227 public void onMeasure(Recycler recycler, State state, int widthSpec, int heightSpec) {
11256 * {@code onMeasure} call. This is because pre-layout means the previous state of the