diff options
| author | Android (Google) Code Review <android-gerrit@google.com> | 2009-05-11 18:26:28 -0700 |
|---|---|---|
| committer | The Android Open Source Project <initial-contribution@android.com> | 2009-05-11 18:26:28 -0700 |
| commit | 72f8accabd3335cd9e7d60f703c1194373d61eb4 (patch) | |
| tree | b5095e53aaa3c76c0e04a05f6e08ae607b987cd4 | |
| parent | 493ab7b29ccbbf9a90a39bfe7d0c8ee07fd7f301 (diff) | |
| parent | f3a6b799102d404e0599d09f37f29a6d482ddb08 (diff) | |
| download | frameworks_native-72f8accabd3335cd9e7d60f703c1194373d61eb4.zip frameworks_native-72f8accabd3335cd9e7d60f703c1194373d61eb4.tar.gz frameworks_native-72f8accabd3335cd9e7d60f703c1194373d61eb4.tar.bz2 | |
am a2ea1d3: Merge change 1371 into donut
Merge commit 'a2ea1d376524346e3f601694751e423ce2711d6b'
* commit 'a2ea1d376524346e3f601694751e423ce2711d6b':
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.
0 files changed, 0 insertions, 0 deletions