commit | 24ba1251583dc637ff1699550aa99811e886b4cf | [log] [tgz] |
---|---|---|
author | Doris Liu <tianliu@google.com> | Tue Mar 15 17:01:55 2016 -0700 |
committer | Doris Liu <tianliu@google.com> | Tue Mar 15 17:01:55 2016 -0700 |
tree | 12488a36100e2f8ca6797cdb28ca087be167ca7c | |
parent | a0021cbb7fe9b1f97c0a31bd0681eb6c0f7f34a9 [diff] |
Workaround for PathMeasure.getSegment() behavior change SkPathMeasure::getSegment(SkScalar startD, SkScalar stopD, SkPath* dst, bool startWithMoveTo) in SkPathMeasure used to ignore the case when startD == stopD in MNC release. In NYC, the same paramaters would yield a tiny segment, which leaves undesirable artifacts as shown in the bug below. Bug: 27665826 Change-Id: I8289dc32773fd55d686458183af44ff072866c6e