On 19 Dec 2008, at 19:26, Jane wrote: > note: i have found that (on mac) linking against an fltk > lib that uses the other renderer (not Quartz) this code > draws like expected, like on the win/linux shots. so the > problem most likely is somewhere inside the Quartz code.
The Quartz back end may well have rendering bugs - there is an implicit pixel offset and scaling involved in matching the FLTK pixel grid to the anti-aliased grid used by Quartz, so it is likely that things could be off-by-one at edges and corners. The older QD code (and the win32 code, and any Xlib code) should be pixel exact. You previous examples suggest that the win32 code my not be pixel exact at the corners either. (OT: Note that Cairo, like Quartz, uses an anti-aliased grid with a half-pixel offset, so it will likely have off-by-one issues also, if we ever use it more widely!) In any case, if you can produce a minimal example that shows the fault, and post it on an STR, we will probably get around to fixing it... In the meantime, you might be able to get the desired result by adding/removing 1 pixel from your dimensions? -- Ian _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
