| commit | 188bfcf7666f4d264329063fd9bf5c44e7734fd8 | [log] [tgz] |
|---|---|---|
| author | reed@google.com <reed@google.com@2bbb7eff-a529-9590-31e7-b0007b416f81> | Tue Jan 17 18:26:38 2012 +0000 |
| committer | reed@google.com <reed@google.com@2bbb7eff-a529-9590-31e7-b0007b416f81> | Tue Jan 17 18:26:38 2012 +0000 |
| tree | 307c8a1d8350b0ae4d3359d13f5e38a060112a5a | |
| parent | 0e06f92bf6853142c7f6850f4e6d7c13c813c39d [diff] |
if the y-max has neighbors (prev and next) with the same Y values, then the cross will be 0, but we can still know the direction by looking at the change in X Fixes the hypen in #7 of this bug http://code.google.com/p/chromium/issues/detail?id=109370 git-svn-id: http://skia.googlecode.com/svn/trunk@3049 2bbb7eff-a529-9590-31e7-b0007b416f81