History log of /frameworks/base/core/jni/android_util_PathParser.cpp
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
b35da390601e3c24e777d72daacd8dbeb4d1d9c4 12-Apr-2016 Doris Liu <tianliu@google.com> Allow leading spaces in path string (to keep behavior consistent)

Bug: 28132454
Change-Id: Iee799c13a85738db3d6940aca0fe917f284fa651
/frameworks/base/core/jni/android_util_PathParser.cpp
0a1a5167be26d363d4e27bdc7b816f425b7b4e66 08-Apr-2016 Doris Liu <tianliu@google.com> Improve error logging for parsing failures

Bug: 27043594
Change-Id: I901b65f734c49444a78e0714e007e15e2340ab9d
/frameworks/base/core/jni/android_util_PathParser.cpp
804618d0863a5d8ad1b08a846bd5319be864a1cb 17-Nov-2015 Doris Liu <tianliu@google.com> VectorDrawable native rendering - Step 2 of MANY

Introduced PathData in Java, which is effectively a thin layer around the
native instance. PathData holds the verbs and points which is being used
in path morphing/interpolation. The verbs and points can be interpreted
into skia path commands, which is now done in native and therefore saves
a handful of JNI calls during path creation.

Removed the old PathDataNode mechanism and changed the PathEvaluator
to use PathData instead.

Also added tests and a microbench. Also ran CTS tests for VectorDrawable
and AnimatedVectorDrawable, and passed all of the existing tests.

Change-Id: Ia166f5172ff031fe18b154327967f911a62caec1
/frameworks/base/core/jni/android_util_PathParser.cpp
1e67f08963cc245660049b6a588483a148955e08 13-Nov-2015 Doris Liu <tianliu@google.com> Add error check for float parsing and fix tests

Change-Id: Ia4f4863d415536b3796edbcdb83c951b6cff02cf
/frameworks/base/core/jni/android_util_PathParser.cpp
cdd23f9d45ea2974c3f295754b89f5462bdd2c0d 11-Nov-2015 Doris Liu <tianliu@google.com> Add hooks in JNI to start using native path parsing

Change-Id: Iaa0d3c2c1936c248146ed7f186a13e8e79be818e
/frameworks/base/core/jni/android_util_PathParser.cpp