>> On 30.07.2009, at 16:48, Jane wrote: >>> a guy sent me a shot of my app running on his system in which the >>> fonts render upside down. any idea what could cause this?
> On 2009-08-02, Matthias Melcher <[email protected]> wrote: >> Thos is a known bug in early ports of FLTK to OS X. It happens if a >> requested font does not exist and the code to flip the (now >> replacement) font is not reached. >> >> This is easily fixable by upgrading to a more recent version of FLTK. >> >> Matthias Sounds to me like if the upside down font is an indication the requested font doesn't exist, you'll probably still need to investigate what fonts do exist, and use those. In your app's case, are you using something like Fl::set_font() to use a font other than the default FLTK font? I'm not sure why, but FLTK's set_font() seems to not return an error code indicating if the font can't be found. (return is void) Not quite sure why this is (anyone?), but maybe you can either request a font you know all machines have, or maybe do a 'precheck' using the native font calls to test if the machine has the font you want, and only use Fl::set_font() if that test passes. I think FLTK's default fonts never have this problem, as it (I think) it only uses fonts that are known to be on each platform. _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
