splitrectfuzz of 32 seems fine. havent checked other architectures/cpus and

engines. this should probably luse the tilebuf size instead of FUZZ anyway so
int is (in theory) settable runtime.


SVN revision: 30198
This commit is contained in:
Carsten Haitzler 2007-06-02 17:35:21 +00:00
parent 7c8c33371d
commit 861fde2fd7
1 changed files with 2 additions and 2 deletions

View File

@ -801,8 +801,8 @@ evas_common_tilebuf_add_redraw(Tilebuf *tb, int x, int y, int w, int h)
rect_init(&r, x, y, w, h);
//fprintf(stderr, "ACCOUNTING: add_redraw: %4d,%4d %3dx%3d\n", x, y, w, h);
//testing on my core2 duo desktop - fuzz of 48 is best.
#define FUZZ 48
//testing on my core2 duo desktop - fuzz of 32 or 48 is best.
#define FUZZ 32
rect_list_add_split_fuzzy_and_merge(&tb->rects, r, FUZZ * FUZZ, FUZZ * FUZZ);
return 1;
#else