summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAndrea Canciani <ranma42@gmail.com>2010-12-16 23:07:30 +0100
committerAndrea Canciani <ranma42@gmail.com>2011-01-02 18:32:46 +0100
commit6472864b2c424c0dfe4ff4e76eff8dfb896e60e8 (patch)
treef6412b9d1c4588dc204839c8f8c22f144047c6eb
parent38dce5d14473e1106c8ea7a67b9be0f400d442a2 (diff)
test: Huge means more than MAX_INT
Cairo makes it possible to create gradients whose extreme objects are defined with double precision coordinates, but it internally represents them with 24.8 fixed point precision. This shows that coordinates that don't fit the valid range are mishandled and don't even trigger an error status.
-rw-r--r--test/huge-linear.c2
-rw-r--r--test/huge-radial.c2
2 files changed, 2 insertions, 2 deletions
diff --git a/test/huge-linear.c b/test/huge-linear.c
index 3d49c2e4..f84b4ea0 100644
--- a/test/huge-linear.c
+++ b/test/huge-linear.c
@@ -27,7 +27,7 @@
#include "cairo-test.h"
/* set this to 0.1 to make this test work */
-#define FACTOR 10
+#define FACTOR 1.e6
/* XXX poppler-cairo doesn't handle gradients very well... */
diff --git a/test/huge-radial.c b/test/huge-radial.c
index a7b50f38..21524b7a 100644
--- a/test/huge-radial.c
+++ b/test/huge-radial.c
@@ -29,7 +29,7 @@
#include "cairo-test.h"
/* set this to 0.1 to make this test work */
-#define FACTOR 10
+#define FACTOR 1.e6
/* XXX poppler-cairo doesn't handle gradients very well... */