tree 1f37e6f71bdce13195b856279628981d60b04b7e
parent 2533ed2e4f99df0e0dd3b05d2212b1881be56765
parent ecadabf578369def58e343c1adbb5537aa9801e4
author Android (Google) Code Review <android-gerrit@google.com> 1242079478 -0700
committer The Android Open Source Project <initial-contribution@android.com> 1242079478 -0700

am ecadabf: Merge change 1372 into donut

Merge commit 'ecadabf578369def58e343c1adbb5537aa9801e4'

* commit 'ecadabf578369def58e343c1adbb5537aa9801e4':
  Fixes #1596240. Optimize invalidate/draw passes by marking opaque views and avoiding drawing them. Whenever a View requests an invalidate its parent check whether the view is opaque or not. When the view is not opaque, the framework behaves as it used to. However, when a view is opaque, the parent marks itself as being dirty because of an opaque view. Its parent then does the same, and so on. When the framework then starts drawing the views, it does not draw views marked as dirty opaque. If a view is dirty opaque and receives an invalidate request from a non-opaque view, it then clears the dirty opaque flag and behaves as before.