diff options
| author | danakj@chromium.org <danakj@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-11-02 20:02:41 +0000 |
|---|---|---|
| committer | danakj@chromium.org <danakj@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-11-02 20:02:41 +0000 |
| commit | 075ae0349a2933720638ef085130efad774d9e37 (patch) | |
| tree | d6a9d3c7f3666431b0534781fd5f3bab1132dfa7 /cc/yuv_video_draw_quad.h | |
| parent | 1bf5a67bf5b09f4338a5df92e3658250b65f8cd3 (diff) | |
| download | chromium_src-075ae0349a2933720638ef085130efad774d9e37.zip chromium_src-075ae0349a2933720638ef085130efad774d9e37.tar.gz chromium_src-075ae0349a2933720638ef085130efad774d9e37.tar.bz2 | |
cc: Replace WebCore::FloatQuad with gfx::QuadF.
It does as it says it does. This depends on the QuadF CL found at
https://codereview.chromium.org/11369043/ and is just search/replace
after that, as I added all the equivalent functionality to QuadF that
we made use of on FloatQuad.
It is possible we may see some slight differences in behaviour from using
FloatQuad, as we should benefit from increased precision, using doubles after
multiplying floats, when using Contains(Point) or IsCounterClockwise().
Covered by existing tests; no dramatic change in behaviour.
R=enne
BUG=147395
Review URL: https://codereview.chromium.org/11364044
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@165735 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'cc/yuv_video_draw_quad.h')
0 files changed, 0 insertions, 0 deletions