On 3 Jul 2007, at 17:41, Carl Ding wrote: > Have tried several ways, but all failed. Anyone met this problem > before?
OK... Short answer *might* be UTF8... Which fltk2 more or less supports and fltk1.1 supports via assorted "unofficial" patches. Longer answer goes something like: Assuming you are using an un- patched fltk1.1.x then; If (1) you know what "code page" is used by the machine your app is running on and (2) what "ASCII" value that particular code page assigns to the "(c)" symbol and (3) the currently selected font has the required glyph at the appropriate code point, then you should be able to draw it simply by setting the appropriate hex value in the output string. In practice, you can't reliably ascertain these three conditions if your app is running on arbitrary hardware outside of your control, so whilst his might work on your development box, it will likely display some arbitrary glyph on an end-users box... And is unlikely to work the same for linux/osx/win32 variants so you would need ifdefs or whatever anyway... Or go with the time-honoured "(c)" solution instead... _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
