delta/cairo.git - gitlab.freedesktop.org: cairo/cairo.git

	Commit message (Collapse)	Author	Age	Files	Lines
*	test/path-precision.c: Correct initialization, error margin for comparisons	Heiko Lewin	2021-02-04	1	-6/+24
\|
*	test: Use ARRAY_LENGTH() macro	Andrea Canciani	2011-03-17	1	-1/+1
\| \| \| \| \|	Some tests hand-code ARRAY_LENGTH(). It is now provided by cairo-test.h, so it can be reused.
*	[test] Track XFAIL using expected results stored as xfail.png	Chris Wilson	2009-07-13	1	-3/+6
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	Instead of tagging the sources, which is insensitive to changes, track the known failure modes by recording the current fail as an xfail.png reference. (We also introduce a new.png to track a fresh error, so that they are not lost in the noise of the old XFAILs and hopefully do not cause everyone to fret). As we have removed the XFAIL tagging we find, surprise surprise, that some tests are now working -- so review all the reference images (as also some .ref.png now should be .xfail.png). Note: I've only checked image,pdf,ps,svg. The test surfaces report some failures that probably need to addressed in source. I've not correct the changes for win32 and quartz. Nor fixed up the experimental backends.
*	[test] Avoid C99 designated initializers	Jeff Muizelaar	2009-02-09	1	-10/+10
\| \| \| \|	MSVC doesn't support these so we shouldn't use them.
*	[test] Check idempotency of append_path() -> copy_path()	Chris Wilson	2008-12-12	1	-0/+108
	The API should preserve the precision across the public interface so that the user is able to retrieve the co-ordinates that he used to construct the path. However since we transform the path to a 24.8 fixed-point internal represent we currently incur a precision-loss - the affects of which can be seen in the miter-precision test case for example. It is planned to move to keeping the path as doubles until the backend explicitly requests the fixed-point coodinates (and some backends, e.g. pdf, might only ever use the doubles). Then, barring rounding errors during path transformations, we should be able to return the exact path the user set (under an identity CTM, of course ;-).