+static const path_test_t polydraw_path[] = {
- {300, 300, 6, 0, 0}, /*0*/
- {150, 200, 2, 0, 0}, /*1*/
- {200, 150, 3, 0, 0}, /*2*/
- {300, 300, 6, 0, 1}, /*3*/
- {300, 300, 2, 0, 0}, /*4*/
- {400, 300, 2, 0, 0}, /*5*/
- {400, 350, 2, 0, 0}, /*6*/
- {50, 100, 6, 0, 0}, /*7*/
- {100, 50, 2, 0, 0}, /*8*/
- {400, 250, 2, 0, 0}, /*9*/
- {500, 300, 2, 0, 0}, /*10*/
- {500, 350, 2, 0, 0}, /*11*/
- {350, 400, 6, 0, 1}, /*12*/
- {600, 200, 2, 0, 1}, /*13*/
- {500, 150, 2, 0, 1}, /*14*/
- {500, 350, 6, 0, 0}, /*15*/
- {500, 150, 2, 0, 0}, /*16*/
- {100, 200, 2, 0, 0}, /*17*/
- {400, 150, 2, 0, 0}, /*18*/
- {400, 350, 2, 0, 0} /*19*/
- };
This is not major, but just thought I'd point out that if you do a set WINETEST_DEBUG=3 on Windows and then call ok_path in your test (you can just do a 0 size when you first make the test for this), you'll get the following output, which seems like it would be both faster to produce and nicer-looking (get the actual PT_'s rather than a number):
static const path_test_t polydraw_path[] = { {300, 300, PT_MOVETO, 0, 0}, /* 0 */ {150, 200, PT_LINETO, 0, 0}, /* 1 */ {200, 150, PT_LINETO | PT_CLOSEFIGURE, 0, 0}, /* 2 */ {300, 300, PT_MOVETO, 0, 0}, /* 3 */ {300, 300, PT_LINETO, 0, 0}, /* 4 */ {400, 300, PT_LINETO, 0, 0}, /* 5 */ {400, 350, PT_LINETO, 0, 0}, /* 6 */ {50, 100, PT_MOVETO, 0, 0}, /* 7 */ {100, 50, PT_LINETO, 0, 0}, /* 8 */ {400, 250, PT_LINETO, 0, 0}, /* 9 */ {500, 300, PT_LINETO, 0, 0}, /* 10 */ {500, 350, PT_LINETO, 0, 0}, /* 11 */ {350, 400, PT_MOVETO, 0, 0}, /* 12 */ {600, 200, PT_LINETO, 0, 0}, /* 13 */ {500, 150, PT_LINETO, 0, 0}, /* 14 */ {500, 350, PT_MOVETO, 0, 0}, /* 15 */ {500, 150, PT_LINETO, 0, 0}, /* 16 */ {100, 200, PT_LINETO, 0, 0}, /* 17 */ {400, 150, PT_LINETO, 0, 0}, /* 18 */ {400, 350, PT_LINETO, 0, 0}}; /* 19 */
Hope this helps.
Misha