summaryrefslogtreecommitdiff
path: root/graphics/java/android/renderscript/ProgramFragmentFixedFunction.java
diff options
context:
space:
mode:
authorChet Haase <chet@google.com>2013-06-10 22:28:58 -0700
committerChet Haase <chet@google.com>2013-09-09 08:39:35 -0700
commit183e2a351daa8071be69eacb514b9405193a7a35 (patch)
tree31c40934d5d108a6db5f516ac8a3fb3bf1d79e37 /graphics/java/android/renderscript/ProgramFragmentFixedFunction.java
parent9b40bdf64420bf1585ccadd36d0a7d38f3c77865 (diff)
Propagate pivot values of 0 to native layer
Logic in pivotXY setters noops when the new value equals the previous value. However, the initial value is "0" even though we actually use a value of the view's midpoint by default. If an app sets a new value of 0, we don't send it down to the native layer because it's the same as the initial value, even though we're actually using a midpoint value instead. This causes a conflict between the matrix used for invalidations (which use the actual values the app set) and the matrix used for rendering (which uses the default midpoint values). The fix is to make sure we send down the initial value, even when it equals the default value, by checking to see whether this is the first time we're setting the pivot. Issue #9337635 Clipping and bad rendering of view corners when y pivot is set Change-Id: I4aa20c4a3c9a866ca17df3e067232b832d0ef504
Diffstat (limited to 'graphics/java/android/renderscript/ProgramFragmentFixedFunction.java')
0 files changed, 0 insertions, 0 deletions