fdo-mirrors/cairo
1
0
Fork 0
mirror of https://gitlab.freedesktop.org/cairo/cairo.git synced 2025-12-20 17:30:07 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions
cairo/test/in-fill-trapezoid.c

280 lines
9.2 KiB
C
Raw Normal View History

[test/in-fill-trapezoid] Add test to exercise _cairo_trap_contains(). A simple test to provide coverage of _cairo_trap_contains(), though not yet seeking boundary conditions.
2008-01-17 11:22:19 +00:00
/*
* Copyright © 2008 Chris Wilson
*
* Permission is hereby granted, free of charge, to any person
* obtaining a copy of this software and associated documentation
* files (the "Software"), to deal in the Software without
* restriction, including without limitation the rights to use, copy,
* modify, merge, publish, distribute, sublicense, and/or sell copies
* of the Software, and to permit persons to whom the Software is
* furnished to do so, subject to the following conditions:
*
* The above copyright notice and this permission notice shall be
* included in all copies or substantial portions of the Software.
*
* THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
* EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
* MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
* NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS
* BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN
* ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
* CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
* SOFTWARE.
*
* Author: Chris Wilson <chris@chris-wilson.co.uk>
*/
#include "cairo-test.h"
static cairo_test_status_t
Remove clip handling from generic surface layer. Handling clip as part of the surface state, as opposed to being part of the operation state, is cumbersome and a hindrance to providing true proxy surface support. For example, the clip must be copied from the surface onto the fallback image, but this was forgotten causing undue hassle in each backend. Another example is the contortion the meta surface endures to ensure the clip is correctly recorded. By contrast passing the clip along with the operation is quite simple and enables us to write generic handlers for providing surface wrappers. (And in the future, we should be able to write more esoteric wrappers, e.g. automatic 2x FSAA, trivially.) In brief, instead of the surface automatically applying the clip before calling the backend, the backend can call into a generic helper to apply clipping. For raster surfaces, clip regions are handled automatically as part of the composite interface. For vector surfaces, a clip helper is introduced to replay and callback into an intersect_clip_path() function as necessary. Whilst this is not primarily a performance related change (the change should just move the computation of the clip from the moment it is applied by the user to the moment it is required by the backend), it is important to track any potential regression: ppc: Speedups ======== image-rgba evolution-20090607-0 1026085.22 0.18% -> 672972.07 0.77%: 1.52x speedup ▌ image-rgba evolution-20090618-0 680579.98 0.12% -> 573237.66 0.16%: 1.19x speedup ▎ image-rgba swfdec-fill-rate-4xaa-0 460296.92 0.36% -> 407464.63 0.42%: 1.13x speedup ▏ image-rgba swfdec-fill-rate-2xaa-0 128431.95 0.47% -> 115051.86 0.42%: 1.12x speedup ▏ Slowdowns ========= image-rgba firefox-periodic-table-0 56837.61 0.78% -> 66055.17 3.20%: 1.09x slowdown ▏
2009-07-23 15:32:13 +01:00
preamble (cairo_test_context_t *ctx)
[test/in-fill-trapezoid] Add test to exercise _cairo_trap_contains(). A simple test to provide coverage of _cairo_trap_contains(), though not yet seeking boundary conditions.
2008-01-17 11:22:19 +00:00
{
cairo_test_status_t ret = CAIRO_TEST_SUCCESS;
Remove clip handling from generic surface layer. Handling clip as part of the surface state, as opposed to being part of the operation state, is cumbersome and a hindrance to providing true proxy surface support. For example, the clip must be copied from the surface onto the fallback image, but this was forgotten causing undue hassle in each backend. Another example is the contortion the meta surface endures to ensure the clip is correctly recorded. By contrast passing the clip along with the operation is quite simple and enables us to write generic handlers for providing surface wrappers. (And in the future, we should be able to write more esoteric wrappers, e.g. automatic 2x FSAA, trivially.) In brief, instead of the surface automatically applying the clip before calling the backend, the backend can call into a generic helper to apply clipping. For raster surfaces, clip regions are handled automatically as part of the composite interface. For vector surfaces, a clip helper is introduced to replay and callback into an intersect_clip_path() function as necessary. Whilst this is not primarily a performance related change (the change should just move the computation of the clip from the moment it is applied by the user to the moment it is required by the backend), it is important to track any potential regression: ppc: Speedups ======== image-rgba evolution-20090607-0 1026085.22 0.18% -> 672972.07 0.77%: 1.52x speedup ▌ image-rgba evolution-20090618-0 680579.98 0.12% -> 573237.66 0.16%: 1.19x speedup ▎ image-rgba swfdec-fill-rate-4xaa-0 460296.92 0.36% -> 407464.63 0.42%: 1.13x speedup ▏ image-rgba swfdec-fill-rate-2xaa-0 128431.95 0.47% -> 115051.86 0.42%: 1.12x speedup ▏ Slowdowns ========= image-rgba firefox-periodic-table-0 56837.61 0.78% -> 66055.17 3.20%: 1.09x slowdown ▏
2009-07-23 15:32:13 +01:00
cairo_surface_t *surface;
cairo_t *cr;
surface = cairo_image_surface_create (CAIRO_FORMAT_ARGB32, 0, 0);
cr = cairo_create (surface);
cairo_surface_destroy (surface);
[test/in-fill-trapezoid] Add test to exercise _cairo_trap_contains(). A simple test to provide coverage of _cairo_trap_contains(), though not yet seeking boundary conditions.
2008-01-17 11:22:19 +00:00
[test/in-fill-trapezoid] Add a few holes. Complete the coverage of _cairo_trap_contains() by cutting holes out of the simple shapes.
2008-01-17 13:13:40 +00:00
cairo_set_fill_rule (cr, CAIRO_FILL_RULE_EVEN_ODD);
[test/in-fill-trapezoid] Add test to exercise _cairo_trap_contains(). A simple test to provide coverage of _cairo_trap_contains(), though not yet seeking boundary conditions.
2008-01-17 11:22:19 +00:00
/* simple rectangle */
cairo_new_path (cr);
cairo_rectangle (cr, -10, -10, 20, 20);
if (! cairo_in_fill (cr, 0, 0)) {
[test] Preparatory work for running under memfault. In order to run under memfault, the framework is first extended to handle running concurrent tests - i.e. multi-threading. (Not that this is a requirement for memfault, instead it shares a common goal of storing per-test data). To that end all the global data is moved into a per-test context and the targets are adjusted to avoid overlap on shared, global resources (such as output files and frame buffers). In order to preserve the simplicity of the standard draw routines, the context is not passed explicitly as a parameter to the routines, but is instead attached to the cairo_t via the user_data. For the masochist, to enable the tests to be run across multiple threads simply set the environment variable CAIRO_TEST_NUM_THREADS to the desired number. In the long run, we can hope the need for memfault (runtime testing of error paths) will be mitigated by static analysis. A promising candidate for this task would appear to be http://hal.cs.berkeley.edu/cil/.
2008-08-11 21:12:45 +01:00
cairo_test_log (ctx, "Error: Failed to find point inside rectangle\n");
[test/in-fill-trapezoid] Add test to exercise _cairo_trap_contains(). A simple test to provide coverage of _cairo_trap_contains(), though not yet seeking boundary conditions.
2008-01-17 11:22:19 +00:00
ret = CAIRO_TEST_FAILURE;
}
[test] Expand in-fill-trapezoid Test vertices and edges of a rectangle to probe 'corner-cases', using the insideness conditions from flash.
2008-11-11 10:22:17 +00:00
/* rectangular boundary tests */
[test] Change test semantics to match new in-fill definition The in-fill definition has changed to include queries on the edges and vertices, so update the test case to match.
2009-05-25 22:10:20 +01:00
if (! cairo_in_fill (cr, -10, -10)) {
cairo_test_log (ctx, "Error: Failed to find top-left vertex inside rectangle\n");
[test] Expand in-fill-trapezoid Test vertices and edges of a rectangle to probe 'corner-cases', using the insideness conditions from flash.
2008-11-11 10:22:17 +00:00
ret = CAIRO_TEST_FAILURE;
}
[test] Change test semantics to match new in-fill definition The in-fill definition has changed to include queries on the edges and vertices, so update the test case to match.
2009-05-25 22:10:20 +01:00
if (! cairo_in_fill (cr, -10, 10)) {
cairo_test_log (ctx, "Error: Failed to find bottom-left vertex inside rectangle\n");
[test] Expand in-fill-trapezoid Test vertices and edges of a rectangle to probe 'corner-cases', using the insideness conditions from flash.
2008-11-11 10:22:17 +00:00
ret = CAIRO_TEST_FAILURE;
}
if (! cairo_in_fill (cr, 10, -10)) {
cairo_test_log (ctx, "Error: Failed to find top-right vertex inside rectangle\n");
ret = CAIRO_TEST_FAILURE;
}
[test] Change test semantics to match new in-fill definition The in-fill definition has changed to include queries on the edges and vertices, so update the test case to match.
2009-05-25 22:10:20 +01:00
if (! cairo_in_fill (cr, 10, 10)) {
cairo_test_log (ctx, "Error: Failed to find bottom-right vertex inside rectangle\n");
[test] Expand in-fill-trapezoid Test vertices and edges of a rectangle to probe 'corner-cases', using the insideness conditions from flash.
2008-11-11 10:22:17 +00:00
ret = CAIRO_TEST_FAILURE;
}
[test] Change test semantics to match new in-fill definition The in-fill definition has changed to include queries on the edges and vertices, so update the test case to match.
2009-05-25 22:10:20 +01:00
if (! cairo_in_fill (cr, -10, 0)) {
cairo_test_log (ctx, "Error: Failed to find left edge inside rectangle\n");
[test] Expand in-fill-trapezoid Test vertices and edges of a rectangle to probe 'corner-cases', using the insideness conditions from flash.
2008-11-11 10:22:17 +00:00
ret = CAIRO_TEST_FAILURE;
}
if (! cairo_in_fill (cr, 0, -10)) {
cairo_test_log (ctx, "Error: Failed to find top edge inside rectangle\n");
ret = CAIRO_TEST_FAILURE;
}
if (! cairo_in_fill (cr, 10, 0)) {
cairo_test_log (ctx, "Error: Failed to find right edge inside rectangle\n");
ret = CAIRO_TEST_FAILURE;
}
[test] Change test semantics to match new in-fill definition The in-fill definition has changed to include queries on the edges and vertices, so update the test case to match.
2009-05-25 22:10:20 +01:00
if (! cairo_in_fill (cr, 0, 10)) {
cairo_test_log (ctx, "Error: Failed to find bottom edge inside rectangle\n");
[test] Expand in-fill-trapezoid Test vertices and edges of a rectangle to probe 'corner-cases', using the insideness conditions from flash.
2008-11-11 10:22:17 +00:00
ret = CAIRO_TEST_FAILURE;
}
[test/in-fill-trapezoid] Add test to exercise _cairo_trap_contains(). A simple test to provide coverage of _cairo_trap_contains(), though not yet seeking boundary conditions.
2008-01-17 11:22:19 +00:00
/* simple circle */
cairo_new_path (cr);
cairo_arc (cr, 0, 0, 10, 0, 2 * M_PI);
if (! cairo_in_fill (cr, 0, 0)) {
Remove clip handling from generic surface layer. Handling clip as part of the surface state, as opposed to being part of the operation state, is cumbersome and a hindrance to providing true proxy surface support. For example, the clip must be copied from the surface onto the fallback image, but this was forgotten causing undue hassle in each backend. Another example is the contortion the meta surface endures to ensure the clip is correctly recorded. By contrast passing the clip along with the operation is quite simple and enables us to write generic handlers for providing surface wrappers. (And in the future, we should be able to write more esoteric wrappers, e.g. automatic 2x FSAA, trivially.) In brief, instead of the surface automatically applying the clip before calling the backend, the backend can call into a generic helper to apply clipping. For raster surfaces, clip regions are handled automatically as part of the composite interface. For vector surfaces, a clip helper is introduced to replay and callback into an intersect_clip_path() function as necessary. Whilst this is not primarily a performance related change (the change should just move the computation of the clip from the moment it is applied by the user to the moment it is required by the backend), it is important to track any potential regression: ppc: Speedups ======== image-rgba evolution-20090607-0 1026085.22 0.18% -> 672972.07 0.77%: 1.52x speedup ▌ image-rgba evolution-20090618-0 680579.98 0.12% -> 573237.66 0.16%: 1.19x speedup ▎ image-rgba swfdec-fill-rate-4xaa-0 460296.92 0.36% -> 407464.63 0.42%: 1.13x speedup ▏ image-rgba swfdec-fill-rate-2xaa-0 128431.95 0.47% -> 115051.86 0.42%: 1.12x speedup ▏ Slowdowns ========= image-rgba firefox-periodic-table-0 56837.61 0.78% -> 66055.17 3.20%: 1.09x slowdown ▏
2009-07-23 15:32:13 +01:00
cairo_test_log (ctx, "Error: Failed to find point inside circle [even-odd]\n");
[test/in-fill-trapezoid] Add test to exercise _cairo_trap_contains(). A simple test to provide coverage of _cairo_trap_contains(), though not yet seeking boundary conditions.
2008-01-17 11:22:19 +00:00
ret = CAIRO_TEST_FAILURE;
}
[test/in-fill-trapezoid] Add a few holes. Complete the coverage of _cairo_trap_contains() by cutting holes out of the simple shapes.
2008-01-17 13:13:40 +00:00
/* holey rectangle */
cairo_new_path (cr);
cairo_rectangle (cr, -10, -10, 20, 20);
cairo_rectangle (cr, -5, -5, 10, 10);
if (cairo_in_fill (cr, 0, 0)) {
[test] Change test semantics to match new in-fill definition The in-fill definition has changed to include queries on the edges and vertices, so update the test case to match.
2009-05-25 22:10:20 +01:00
cairo_test_log (ctx, "Error: Found an unexpected point inside rectangular eo-hole\n");
[test/in-fill-trapezoid] Add a few holes. Complete the coverage of _cairo_trap_contains() by cutting holes out of the simple shapes.
2008-01-17 13:13:40 +00:00
ret = CAIRO_TEST_FAILURE;
}
/* holey circle */
cairo_new_path (cr);
cairo_arc (cr, 0, 0, 10, 0, 2 * M_PI);
cairo_arc (cr, 0, 0, 5, 0, 2 * M_PI);
if (cairo_in_fill (cr, 0, 0)) {
[test] Change test semantics to match new in-fill definition The in-fill definition has changed to include queries on the edges and vertices, so update the test case to match.
2009-05-25 22:10:20 +01:00
cairo_test_log (ctx, "Error: Found an unexpected point inside circular eo-hole\n");
[test/in-fill-trapezoid] Add a few holes. Complete the coverage of _cairo_trap_contains() by cutting holes out of the simple shapes.
2008-01-17 13:13:40 +00:00
ret = CAIRO_TEST_FAILURE;
}
[test] Add WINDING variants to in-fill test Check cairo_in_fill() with some WINDING tests as well as the current EVEN_ODD.
2008-11-06 00:04:11 +00:00
cairo_set_fill_rule (cr, CAIRO_FILL_RULE_WINDING);
/* simple rectangle */
cairo_new_path (cr);
cairo_rectangle (cr, -10, -10, 20, 20);
if (! cairo_in_fill (cr, 0, 0)) {
cairo_test_log (ctx, "Error: Failed to find point inside rectangle\n");
ret = CAIRO_TEST_FAILURE;
}
/* simple circle */
cairo_new_path (cr);
cairo_arc (cr, 0, 0, 10, 0, 2 * M_PI);
if (! cairo_in_fill (cr, 0, 0)) {
Remove clip handling from generic surface layer. Handling clip as part of the surface state, as opposed to being part of the operation state, is cumbersome and a hindrance to providing true proxy surface support. For example, the clip must be copied from the surface onto the fallback image, but this was forgotten causing undue hassle in each backend. Another example is the contortion the meta surface endures to ensure the clip is correctly recorded. By contrast passing the clip along with the operation is quite simple and enables us to write generic handlers for providing surface wrappers. (And in the future, we should be able to write more esoteric wrappers, e.g. automatic 2x FSAA, trivially.) In brief, instead of the surface automatically applying the clip before calling the backend, the backend can call into a generic helper to apply clipping. For raster surfaces, clip regions are handled automatically as part of the composite interface. For vector surfaces, a clip helper is introduced to replay and callback into an intersect_clip_path() function as necessary. Whilst this is not primarily a performance related change (the change should just move the computation of the clip from the moment it is applied by the user to the moment it is required by the backend), it is important to track any potential regression: ppc: Speedups ======== image-rgba evolution-20090607-0 1026085.22 0.18% -> 672972.07 0.77%: 1.52x speedup ▌ image-rgba evolution-20090618-0 680579.98 0.12% -> 573237.66 0.16%: 1.19x speedup ▎ image-rgba swfdec-fill-rate-4xaa-0 460296.92 0.36% -> 407464.63 0.42%: 1.13x speedup ▏ image-rgba swfdec-fill-rate-2xaa-0 128431.95 0.47% -> 115051.86 0.42%: 1.12x speedup ▏ Slowdowns ========= image-rgba firefox-periodic-table-0 56837.61 0.78% -> 66055.17 3.20%: 1.09x slowdown ▏
2009-07-23 15:32:13 +01:00
cairo_test_log (ctx, "Error: Failed to find point inside circle [nonzero]\n");
[test] Add WINDING variants to in-fill test Check cairo_in_fill() with some WINDING tests as well as the current EVEN_ODD.
2008-11-06 00:04:11 +00:00
ret = CAIRO_TEST_FAILURE;
}
/* overlapping circle/rectangle */
cairo_new_path (cr);
cairo_rectangle (cr, -10, -10, 20, 20);
cairo_new_sub_path (cr);
cairo_arc (cr, 0, 0, 10, 0, 2 * M_PI);
if (! cairo_in_fill (cr, 0, 0)) {
cairo_test_log (ctx, "Error: Failed to find point inside circle+rectangle\n");
ret = CAIRO_TEST_FAILURE;
}
/* holey rectangle */
cairo_new_path (cr);
cairo_rectangle (cr, -10, -10, 20, 20);
cairo_rectangle (cr, 5, -5, -10, 10);
if (cairo_in_fill (cr, 0, 0)) {
[test] Change test semantics to match new in-fill definition The in-fill definition has changed to include queries on the edges and vertices, so update the test case to match.
2009-05-25 22:10:20 +01:00
cairo_test_log (ctx, "Error: Found an unexpected point inside rectangular non-zero-hole\n");
[test] Add WINDING variants to in-fill test Check cairo_in_fill() with some WINDING tests as well as the current EVEN_ODD.
2008-11-06 00:04:11 +00:00
ret = CAIRO_TEST_FAILURE;
}
/* holey circle */
cairo_new_path (cr);
cairo_arc (cr, 0, 0, 10, 0, 2 * M_PI);
cairo_arc_negative (cr, 0, 0, 5, 0, -2 * M_PI);
if (cairo_in_fill (cr, 0, 0)) {
[test] Change test semantics to match new in-fill definition The in-fill definition has changed to include queries on the edges and vertices, so update the test case to match.
2009-05-25 22:10:20 +01:00
cairo_test_log (ctx, "Error: Found an unexpected point inside circular non-zero-hole\n");
[test] Add WINDING variants to in-fill test Check cairo_in_fill() with some WINDING tests as well as the current EVEN_ODD.
2008-11-06 00:04:11 +00:00
ret = CAIRO_TEST_FAILURE;
}
/* not a holey circle */
cairo_new_path (cr);
cairo_arc (cr, 0, 0, 10, 0, 2 * M_PI);
cairo_arc (cr, 0, 0, 5, 0, 2 * M_PI);
if (! cairo_in_fill (cr, 0, 0)) {
cairo_test_log (ctx, "Error: Failed to find point inside two circles\n");
ret = CAIRO_TEST_FAILURE;
}
[test] Add off-centre tests to in-fill-trapezoid. Reading through the previous commit spotted that the arguments to edge_compare_for_y_against_x were transposed, but the test-suite had failed to catch detect it. This is due that in order to actually solve the equation we need to have a diagonal edge passing near an off-centre point of interest, which was not among the test cases. So add some off-centre tests to fully exercise the code.
2008-11-06 01:02:23 +00:00
/* check off-centre */
cairo_new_path (cr);
cairo_arc (cr, 7.5, 0, 10, 0, 2 * M_PI);
cairo_arc_negative (cr, 7.5, 0, 5, 0, -2 * M_PI);
if (cairo_in_fill (cr, 7.5, 0)) {
[test] Change test semantics to match new in-fill definition The in-fill definition has changed to include queries on the edges and vertices, so update the test case to match.
2009-05-25 22:10:20 +01:00
cairo_test_log (ctx, "Error: Found an unexpected point inside off-centre-x circular non-zero-hole\n");
[test] Add off-centre tests to in-fill-trapezoid. Reading through the previous commit spotted that the arguments to edge_compare_for_y_against_x were transposed, but the test-suite had failed to catch detect it. This is due that in order to actually solve the equation we need to have a diagonal edge passing near an off-centre point of interest, which was not among the test cases. So add some off-centre tests to fully exercise the code.
2008-11-06 01:02:23 +00:00
ret = CAIRO_TEST_FAILURE;
}
cairo_new_path (cr);
cairo_arc (cr, 0, 7.5, 10, 0, 2 * M_PI);
cairo_arc_negative (cr, 0, 7.5, 5, 0, -2 * M_PI);
if (cairo_in_fill (cr, 0, 7.5)) {
[test] Change test semantics to match new in-fill definition The in-fill definition has changed to include queries on the edges and vertices, so update the test case to match.
2009-05-25 22:10:20 +01:00
cairo_test_log (ctx, "Error: Found an unexpected point inside off-centre-y circular non-zero-hole\n");
[test] Add off-centre tests to in-fill-trapezoid. Reading through the previous commit spotted that the arguments to edge_compare_for_y_against_x were transposed, but the test-suite had failed to catch detect it. This is due that in order to actually solve the equation we need to have a diagonal edge passing near an off-centre point of interest, which was not among the test cases. So add some off-centre tests to fully exercise the code.
2008-11-06 01:02:23 +00:00
ret = CAIRO_TEST_FAILURE;
}
cairo_new_path (cr);
cairo_arc (cr, 15, 0, 10, 0, 2 * M_PI);
if (! cairo_in_fill (cr, 15, 0)) {
[test] Change test semantics to match new in-fill definition The in-fill definition has changed to include queries on the edges and vertices, so update the test case to match.
2009-05-25 22:10:20 +01:00
cairo_test_log (ctx, "Error: Failed to find point inside off-centre-x circle\n");
[test] Add off-centre tests to in-fill-trapezoid. Reading through the previous commit spotted that the arguments to edge_compare_for_y_against_x were transposed, but the test-suite had failed to catch detect it. This is due that in order to actually solve the equation we need to have a diagonal edge passing near an off-centre point of interest, which was not among the test cases. So add some off-centre tests to fully exercise the code.
2008-11-06 01:02:23 +00:00
ret = CAIRO_TEST_FAILURE;
}
cairo_new_path (cr);
cairo_arc (cr, 0, 15, 10, 0, 2 * M_PI);
if (! cairo_in_fill (cr, 0, 15)) {
[test] Change test semantics to match new in-fill definition The in-fill definition has changed to include queries on the edges and vertices, so update the test case to match.
2009-05-25 22:10:20 +01:00
cairo_test_log (ctx, "Error: Failed to find point inside off-centre-y circle\n");
[test] Add off-centre tests to in-fill-trapezoid. Reading through the previous commit spotted that the arguments to edge_compare_for_y_against_x were transposed, but the test-suite had failed to catch detect it. This is due that in order to actually solve the equation we need to have a diagonal edge passing near an off-centre point of interest, which was not among the test cases. So add some off-centre tests to fully exercise the code.
2008-11-06 01:02:23 +00:00
ret = CAIRO_TEST_FAILURE;
}
/* simple rectangle */
cairo_new_path (cr);
cairo_rectangle (cr, 10, 0, 5, 5);
if (cairo_in_fill (cr, 0, 0)) {
cairo_test_log (ctx, "Error: Found an unexpected point outside rectangle\n");
ret = CAIRO_TEST_FAILURE;
}
if (cairo_in_fill (cr, 20, 20)) {
cairo_test_log (ctx, "Error: Found an unexpected point outside rectangle\n");
ret = CAIRO_TEST_FAILURE;
}
if (! cairo_in_fill (cr, 12.5, 2.5)) {
cairo_test_log (ctx, "Error: Failed to find point inside rectangle\n");
ret = CAIRO_TEST_FAILURE;
}
/* off-centre triangle */
cairo_new_path (cr);
cairo_move_to (cr, 10, 0);
cairo_line_to (cr, 15, 5);
cairo_line_to (cr, 5, 5);
cairo_close_path (cr);
if (cairo_in_fill (cr, 0, 0) ||
[test] Change test semantics to match new in-fill definition The in-fill definition has changed to include queries on the edges and vertices, so update the test case to match.
2009-05-25 22:10:20 +01:00
cairo_in_fill (cr, 5, 0) ||
cairo_in_fill (cr, 15, 0) ||
[test] Add off-centre tests to in-fill-trapezoid. Reading through the previous commit spotted that the arguments to edge_compare_for_y_against_x were transposed, but the test-suite had failed to catch detect it. This is due that in order to actually solve the equation we need to have a diagonal edge passing near an off-centre point of interest, which was not among the test cases. So add some off-centre tests to fully exercise the code.
2008-11-06 01:02:23 +00:00
cairo_in_fill (cr, 20, 0) ||
[test] Change test semantics to match new in-fill definition The in-fill definition has changed to include queries on the edges and vertices, so update the test case to match.
2009-05-25 22:10:20 +01:00
cairo_in_fill (cr, 0, 10) ||
cairo_in_fill (cr, 10, 10) ||
cairo_in_fill (cr, 20, 10) ||
[test] Add off-centre tests to in-fill-trapezoid. Reading through the previous commit spotted that the arguments to edge_compare_for_y_against_x were transposed, but the test-suite had failed to catch detect it. This is due that in order to actually solve the equation we need to have a diagonal edge passing near an off-centre point of interest, which was not among the test cases. So add some off-centre tests to fully exercise the code.
2008-11-06 01:02:23 +00:00
cairo_in_fill (cr, 7, 2.5) ||
cairo_in_fill (cr, 13, 2.5))
{
[test] Change test semantics to match new in-fill definition The in-fill definition has changed to include queries on the edges and vertices, so update the test case to match.
2009-05-25 22:10:20 +01:00
cairo_test_log (ctx,
"Error: Found an unexpected point outside triangle\n"
"\t(0, 0) -> %s\n"
"\t(5, 0) -> %s\n"
"\t(15, 0) -> %s\n"
"\t(20, 0) -> %s\n"
"\t(0, 10) -> %s\n"
"\t(10, 10) -> %s\n"
"\t(20, 10) -> %s\n"
"\t(7, 2.5) -> %s\n"
"\t(13, 2.5) -> %s\n",
cairo_in_fill (cr, 0, 0) ? "inside" : "outside",
cairo_in_fill (cr, 5, 0) ? "inside" : "outside",
cairo_in_fill (cr, 15, 0) ? "inside" : "outside",
cairo_in_fill (cr, 20, 0) ? "inside" : "outside",
cairo_in_fill (cr, 0, 10) ? "inside" : "outside",
cairo_in_fill (cr, 10, 10) ? "inside" : "outside",
cairo_in_fill (cr, 20, 10) ? "inside" : "outside",
cairo_in_fill (cr, 7, 2.5) ? "inside" : "outside",
cairo_in_fill (cr, 13, 2.5) ? "inside" : "outside");
ret = CAIRO_TEST_FAILURE;
}
if (! cairo_in_fill (cr, 7.5, 2.5) ||
! cairo_in_fill (cr, 12.5, 2.5) ||
! cairo_in_fill (cr, 10, 5))
{
cairo_test_log (ctx,
"Error: Failed to find point on triangle edge\n"
"\t(7.5, 2.5) -> %s\n"
"\t(12.5, 2.5) -> %s\n"
"\t(10, 5) -> %s\n",
cairo_in_fill (cr, 7.5, 2.5) ? "inside" : "outside",
cairo_in_fill (cr, 12.5, 2.5) ? "inside" : "outside",
cairo_in_fill (cr, 10, 5) ? "inside" : "outside");
[test] Add off-centre tests to in-fill-trapezoid. Reading through the previous commit spotted that the arguments to edge_compare_for_y_against_x were transposed, but the test-suite had failed to catch detect it. This is due that in order to actually solve the equation we need to have a diagonal edge passing near an off-centre point of interest, which was not among the test cases. So add some off-centre tests to fully exercise the code.
2008-11-06 01:02:23 +00:00
ret = CAIRO_TEST_FAILURE;
}
if (! cairo_in_fill (cr, 8, 2.5) ||
! cairo_in_fill (cr, 12, 2.5))
{
cairo_test_log (ctx, "Error: Failed to find point inside triangle\n");
ret = CAIRO_TEST_FAILURE;
}
Remove clip handling from generic surface layer. Handling clip as part of the surface state, as opposed to being part of the operation state, is cumbersome and a hindrance to providing true proxy surface support. For example, the clip must be copied from the surface onto the fallback image, but this was forgotten causing undue hassle in each backend. Another example is the contortion the meta surface endures to ensure the clip is correctly recorded. By contrast passing the clip along with the operation is quite simple and enables us to write generic handlers for providing surface wrappers. (And in the future, we should be able to write more esoteric wrappers, e.g. automatic 2x FSAA, trivially.) In brief, instead of the surface automatically applying the clip before calling the backend, the backend can call into a generic helper to apply clipping. For raster surfaces, clip regions are handled automatically as part of the composite interface. For vector surfaces, a clip helper is introduced to replay and callback into an intersect_clip_path() function as necessary. Whilst this is not primarily a performance related change (the change should just move the computation of the clip from the moment it is applied by the user to the moment it is required by the backend), it is important to track any potential regression: ppc: Speedups ======== image-rgba evolution-20090607-0 1026085.22 0.18% -> 672972.07 0.77%: 1.52x speedup ▌ image-rgba evolution-20090618-0 680579.98 0.12% -> 573237.66 0.16%: 1.19x speedup ▎ image-rgba swfdec-fill-rate-4xaa-0 460296.92 0.36% -> 407464.63 0.42%: 1.13x speedup ▏ image-rgba swfdec-fill-rate-2xaa-0 128431.95 0.47% -> 115051.86 0.42%: 1.12x speedup ▏ Slowdowns ========= image-rgba firefox-periodic-table-0 56837.61 0.78% -> 66055.17 3.20%: 1.09x slowdown ▏
2009-07-23 15:32:13 +01:00
cairo_destroy (cr);
[test/in-fill-trapezoid] Add test to exercise _cairo_trap_contains(). A simple test to provide coverage of _cairo_trap_contains(), though not yet seeking boundary conditions.
2008-01-17 11:22:19 +00:00
return ret;
}
[test] Build test suite into single binary. Avoid calling libtool to link every single test case, by building just one binary from all the sources. This binary is then given the task of choosing tests to run (based on user selection and individual test requirement), forking each test into its own process and accumulating the results.
2008-09-03 16:38:03 +01:00
CAIRO_TEST (in_fill_trapezoid,
Remove clip handling from generic surface layer. Handling clip as part of the surface state, as opposed to being part of the operation state, is cumbersome and a hindrance to providing true proxy surface support. For example, the clip must be copied from the surface onto the fallback image, but this was forgotten causing undue hassle in each backend. Another example is the contortion the meta surface endures to ensure the clip is correctly recorded. By contrast passing the clip along with the operation is quite simple and enables us to write generic handlers for providing surface wrappers. (And in the future, we should be able to write more esoteric wrappers, e.g. automatic 2x FSAA, trivially.) In brief, instead of the surface automatically applying the clip before calling the backend, the backend can call into a generic helper to apply clipping. For raster surfaces, clip regions are handled automatically as part of the composite interface. For vector surfaces, a clip helper is introduced to replay and callback into an intersect_clip_path() function as necessary. Whilst this is not primarily a performance related change (the change should just move the computation of the clip from the moment it is applied by the user to the moment it is required by the backend), it is important to track any potential regression: ppc: Speedups ======== image-rgba evolution-20090607-0 1026085.22 0.18% -> 672972.07 0.77%: 1.52x speedup ▌ image-rgba evolution-20090618-0 680579.98 0.12% -> 573237.66 0.16%: 1.19x speedup ▎ image-rgba swfdec-fill-rate-4xaa-0 460296.92 0.36% -> 407464.63 0.42%: 1.13x speedup ▏ image-rgba swfdec-fill-rate-2xaa-0 128431.95 0.47% -> 115051.86 0.42%: 1.12x speedup ▏ Slowdowns ========= image-rgba firefox-periodic-table-0 56837.61 0.78% -> 66055.17 3.20%: 1.09x slowdown ▏
2009-07-23 15:32:13 +01:00
"Test cairo_in_fill",
[test] Build test suite into single binary. Avoid calling libtool to link every single test case, by building just one binary from all the sources. This binary is then given the task of choosing tests to run (based on user selection and individual test requirement), forking each test into its own process and accumulating the results.
2008-09-03 16:38:03 +01:00
"in, trap", /* keywords */
NULL, /* requirements */
0, 0,
Remove clip handling from generic surface layer. Handling clip as part of the surface state, as opposed to being part of the operation state, is cumbersome and a hindrance to providing true proxy surface support. For example, the clip must be copied from the surface onto the fallback image, but this was forgotten causing undue hassle in each backend. Another example is the contortion the meta surface endures to ensure the clip is correctly recorded. By contrast passing the clip along with the operation is quite simple and enables us to write generic handlers for providing surface wrappers. (And in the future, we should be able to write more esoteric wrappers, e.g. automatic 2x FSAA, trivially.) In brief, instead of the surface automatically applying the clip before calling the backend, the backend can call into a generic helper to apply clipping. For raster surfaces, clip regions are handled automatically as part of the composite interface. For vector surfaces, a clip helper is introduced to replay and callback into an intersect_clip_path() function as necessary. Whilst this is not primarily a performance related change (the change should just move the computation of the clip from the moment it is applied by the user to the moment it is required by the backend), it is important to track any potential regression: ppc: Speedups ======== image-rgba evolution-20090607-0 1026085.22 0.18% -> 672972.07 0.77%: 1.52x speedup ▌ image-rgba evolution-20090618-0 680579.98 0.12% -> 573237.66 0.16%: 1.19x speedup ▎ image-rgba swfdec-fill-rate-4xaa-0 460296.92 0.36% -> 407464.63 0.42%: 1.13x speedup ▏ image-rgba swfdec-fill-rate-2xaa-0 128431.95 0.47% -> 115051.86 0.42%: 1.12x speedup ▏ Slowdowns ========= image-rgba firefox-periodic-table-0 56837.61 0.78% -> 66055.17 3.20%: 1.09x slowdown ▏
2009-07-23 15:32:13 +01:00
preamble, NULL)
Reference in a new issue Copy permalink