tree 7397a7b18c5731e1350f15ff9e9855443261b8d5
parent 8ee6f8f77e9fe066a18bb68bf0cf6c3f33dde3ef
parent 2a98fb9fb1eda1f18cf1555634a7c33f3147234c
author Android (Google) Code Review <android-gerrit@google.com> 1242075863 -0700
committer Android (Google) Code Review <android-gerrit@google.com> 1242075863 -0700

Merge change 1371 into donut

* changes:
  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.