Changed maxInputCount for exact inputCount
Processing still had issue when the number of inputs was 0, so I changed my previous fix from a maximum input count to an exact input count. -1 is used when the input count isn't fixed (but still has to be a non-negative number).
BUG=
R=senorblanco@chromium.org, reed@google.com, sugoi@google.com, bsalomon@google.com
Author: sugoi@chromium.org
Review URL: https://codereview.chromium.org/100803004
git-svn-id: http://skia.googlecode.com/svn/trunk@12492 2bbb7eff-a529-9590-31e7-b0007b416f81
diff --git a/src/animator/SkScript.cpp b/src/animator/SkScript.cpp
index c74b195..934b0ab 100644
--- a/src/animator/SkScript.cpp
+++ b/src/animator/SkScript.cpp
@@ -1532,11 +1532,11 @@
SkString* strPtr = new SkString();
SkASSERT(engine);
engine->track(strPtr);
- if (type == SkType_Int)
+ if (type == SkType_Int) {
strPtr->appendS32(operand.fS32);
- else if (type == SkType_Displayable)
+ } else if (type == SkType_Displayable) {
SkASSERT(0); // must call through instance version instead of static version
- else {
+ } else {
if (type != SkType_Float) {
success = false;
break;