summaryrefslogtreecommitdiff
path: root/rs/java/android/renderscript/ProgramVertexFixedFunction.java
diff options
context:
space:
mode:
authorPhil Weaver <pweaver@google.com>2017-04-24 13:23:10 -0700
committerPhil Weaver <pweaver@google.com>2017-04-24 13:23:10 -0700
commite28c03b620c3252b1c24fc326a3a9b4af93ce722 (patch)
tree3f6796e4a319c2d651c3b30e5577ee9c8750ae20 /rs/java/android/renderscript/ProgramVertexFixedFunction.java
parent4a5ea54710b83666b455b3daff740c195f2b0277 (diff)
Use newest scrap view in ListView
When a ListView's contents change, it first measures, using a view at position 0. It then scraps that view, and then scraps all of its other views. Two scrap views thus exist for position 0. Since we were retrieving the oldest scrap view, we would toggle between two different views at position 0. This toggling confuses accessibility. This change takes the newest view from the scap heap, so the view that was recycled last (which is the one shown on the screen) is re-used for the screen. The view used for measuring sticks around and is available for measure again. Bug: 33788047 Test: I verified that the switch state is announced correctly for the cases found in the bug. Change-Id: I936e5ad09c3594e33e80dc39236025bf8bc877b8
Diffstat (limited to 'rs/java/android/renderscript/ProgramVertexFixedFunction.java')
0 files changed, 0 insertions, 0 deletions