summaryrefslogtreecommitdiff
path: root/graphics/java/android/renderscript/RenderScript.java
diff options
context:
space:
mode:
authorChet Haase <chet@google.com>2013-05-03 15:25:33 -0700
committerChet Haase <chet@google.com>2013-05-03 15:32:48 -0700
commit259b696b00f07938569fc9a0ea43858cdaab909b (patch)
tree28a8c0f7ce807599e8fdaf9202022a41c2dafb90 /graphics/java/android/renderscript/RenderScript.java
parent55a08c5ab91014eb42ecdc9e7039c7bae1f00058 (diff)
Fix scaled-view droppings artifact
Sometimes views that are scaled leave behind rows/columns on the screen as they move/scale around. The problem was that the pivot point around which the scale takes place (in the default case of scaling around the center of the view) was getting truncated to integer coordinates in the display list. Meanwhile, the pivot point at the Java level was using the true float values, resulting in a mis-match between the invalidation rectangle (computed at the Java level) and the drawing-operation rectangle (computed at the native level). This only occurred when views had odd bounds (thus the integer representation of the center differed from the float representation of the center), and only when some other drawing operation would expand the clip rect to allow the incorrect drawing operation (using the wrong pivot point) to draw outside of its clip boundaries. Issue #8617023 7x7 screen not updated correctly Change-Id: If88889b9450d34535df732b78077a29b1f24802d
Diffstat (limited to 'graphics/java/android/renderscript/RenderScript.java')
0 files changed, 0 insertions, 0 deletions