summaryrefslogtreecommitdiffstats
path: root/docs/html/sdk/api_diff/16/changes/android.database.sqlite.SQLiteOpenHelper.html
diff options
context:
space:
mode:
authorChet Haase <chet@google.com>2012-07-03 14:17:57 -0700
committerChet Haase <chet@google.com>2012-07-12 14:40:28 -0700
commit0f8e402e954c6e37102fa70f81a1d8ec47156338 (patch)
treede1700e613f2d93330c2a1d1ad287c0f6c11e9c1 /docs/html/sdk/api_diff/16/changes/android.database.sqlite.SQLiteOpenHelper.html
parentc03f0a15578223208b48c1d946872d22a233ede4 (diff)
downloadframeworks_base-0f8e402e954c6e37102fa70f81a1d8ec47156338.zip
frameworks_base-0f8e402e954c6e37102fa70f81a1d8ec47156338.tar.gz
frameworks_base-0f8e402e954c6e37102fa70f81a1d8ec47156338.tar.bz2
Force invalidates on non-visible views. DO NOT MERGE
An optimization prunes invalidates on views which are not inside their parent's bounds. This works in most cases, but it is possible to run a situation where a view has been invalidated (and is thus waiting to be redrawn), but the pruning logic ensures that that draw call will not happen. Further, when/if the view comes into the bounds of its parent again, it may still not be redrawn, because now future invalidates on the view are noop'd because it is already in an invalidated state (and thus will not propagate invalidates up the hierarchy). The fix is to remove the optitmization. This will cause some overhead sending the invalidation request up to the view root, but this overhead is minimal (and only extra for cases of out-of-bounds views), and the more expensive part of rendering these views will still not be done since the view root will avoid re-drawing the hierarchy when the dirty rectangle is empty. Issue #6813661 offscreen views don't get invalidated properly (may remain invisible when returning onscreen) Change-Id: Ic4b439540084a7163be9afc585bea6560d073280
Diffstat (limited to 'docs/html/sdk/api_diff/16/changes/android.database.sqlite.SQLiteOpenHelper.html')
0 files changed, 0 insertions, 0 deletions