skia - 2D graphics library

	Commit message (Collapse)	Author	Age
*	Result of running tools/sanitize_source_files.py (which was added in ↵	rmistry@google.com	2012-08-23
\| \| \| \| \| \| \| \| \|	https://codereview.appspot.com/6465078/) This CL is part II of IV (I broke down the 1280 files into 4 CLs). Review URL: https://codereview.appspot.com/6474054 git-svn-id: http://skia.googlecode.com/svn/trunk@5263 2bbb7eff-a529-9590-31e7-b0007b416f81
*	Even when the pts are restricted to 32K values, we can still overflow computing	reed@google.com	2012-08-06
\| \| \| \| \| \| \| \| \| \| \|	a fixed-point coefficient for quadratics. To avoid this, we bias these coefficients, storing 1/2 of their actual value, and then apply the 2x unbias in updateQuadratic(). Fixes http://code.google.com/p/chromium/issues/detail?id=140803 Review URL: https://codereview.appspot.com/6450099 git-svn-id: http://skia.googlecode.com/svn/trunk@4960 2bbb7eff-a529-9590-31e7-b0007b416f81
*	If we lose precision computing sum of the dash intervals, then we can have the	reed@google.com	2012-08-06
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	same error when we subtract-in-a-loop with the phase. The result is that we can read past the end of the array. To fix this, we just pin the loop counter, and if we exhaust our intervals, we just treat the phase as 0. Not precisely the exact answer, but we aren't going to draw this dash correctly anyway, since it contains massive interval values that will be imprecise given our current float implementation. Fixes http://code.google.com/p/chromium/issues/detail?id=140642 Review URL: https://codereview.appspot.com/6458088 git-svn-id: http://skia.googlecode.com/svn/trunk@4959 2bbb7eff-a529-9590-31e7-b0007b416f81
*	add test for http://code.google.com/p/chromium/issues/detail?id=131181	reed@google.com	2012-06-15
\| \| \| \|	git-svn-id: http://skia.googlecode.com/svn/trunk@4266 2bbb7eff-a529-9590-31e7-b0007b416f81
*	fix bug (and add test) for drawing an inverse-path whose bounds do intersect	reed@google.com	2012-05-01
\| \| \| \| \| \| \| \| \|	the clip, but whose edges do not (e.g. a curve). We used to overdraw a section (and assert). git-svn-id: http://skia.googlecode.com/svn/trunk@3809 2bbb7eff-a529-9590-31e7-b0007b416f81
*	check for numerical imprecision on phase	reed@google.com	2012-04-24
\| \| \| \| \| \| \| \|	fixes http://code.google.com/p/chromium/issues/detail?id=124652 git-svn-id: http://skia.googlecode.com/svn/trunk@3761 2bbb7eff-a529-9590-31e7-b0007b416f81
*	fix clamping when we chop a cubic	reed@google.com	2012-04-16
\| \| \| \| \| \|	Review URL: https://codereview.appspot.com/6039048 git-svn-id: http://skia.googlecode.com/svn/trunk@3691 2bbb7eff-a529-9590-31e7-b0007b416f81
*	dd DrawPathTest to gyp	mike@reedtribe.org	2012-04-14
\| \| \| \| \| \| \| \|	add regression tests for bug 533 git-svn-id: http://skia.googlecode.com/svn/trunk@3678 2bbb7eff-a529-9590-31e7-b0007b416f81
*	always allocate (only) the width of the clip for the AA row, since it will	reed@google.com	2012-02-23
	already be clamped to 32K (our impl limit at the moment.) add unittest to confirm this fix git-svn-id: http://skia.googlecode.com/svn/trunk@3242 2bbb7eff-a529-9590-31e7-b0007b416f81