summaryrefslogtreecommitdiff
path: root/docs/html/sdk/api_diff/12/changes
diff options
context:
space:
mode:
authorChet Haase <chet@google.com>2012-08-30 17:20:08 -0700
committerChet Haase <chet@google.com>2012-08-30 17:36:54 -0700
commitca479d468be963661fd82634f4b57f21c13f1fe6 (patch)
treef422533da269f8f83ecc9be0de6e524e9aad50aa /docs/html/sdk/api_diff/12/changes
parent71d7c3c628fbce04b8bdb60f127588ada00bae13 (diff)
Make detachViewFromParent more robust
Calling detachViewFromParent() without calling remove or attach in the same drawing frame could, in some situations, cause a crash in the native DisplayList code. detach/attach are intended to be very lightweight and do not manage the native DisplayList content the same way that add/remove do. Nor do they cause an invalidate() or requestLayout(), which would cause the native structures to get recreated appropriately. This fix makes this process more robust in two ways: - DisplayLists should not get finalized (therefore destroying their native structures) when there are still parent DisplayLists referring to them (each DisplayList keeps references to its child DisplayLists). This will prevent the native crash associated with unmatched detach*() calls. - The docs for detach/attach have been enhanced to make it easier for developers to understand how to use these methods more correctly and successfully. Issue #7064818 detachViewFromParent() should be more robust Change-Id: I53befc04d5d58c225060f397725566d470488c9b
Diffstat (limited to 'docs/html/sdk/api_diff/12/changes')
0 files changed, 0 insertions, 0 deletions