On 17.07.2012, at 16:33, darren legge wrote: > I am using Xfbdev (tinyx / kdrive) on an arm target and am just moving an > fltk 1.1.7 application to fltk 1.3, using utf8 and pcf fonts. > For me, the speed of drawing is not perceptibly different so maybe the > slowness you see is a nanoX issue. > My issue is the time it takes the fltk application to start up the first time > after boot - 37 seconds ! > If I re-compile fltk to not use xft then it starts much quicker (4 seconds) > but utf8 characters do not show correctly. I thought xft was just > anti-aliasing (which won't work with pcf fonts anyway). It seems xft is > required for utf8 to work though - is this true ? > I can reduce the startup time by removing some fonts but even with just a > couple of chinese fonts the startup time is the wrong side of 10 seconds. > Is there a trick to improve this - can fltk somehow cache the fonts it is > scanning over a reboot ?
Hmm, that is too long. 34 seconds. In the OS X implementation, FLTK loads only the characters that are actually needed. It used to load pages of characters (1024, IIRC), but that would delay a popup menu for three seconds the first time it opened (OSX uses special characters in popup menus). By caching single characters, the delay became unnoticeable. Maybe this can be ported to X/Xft? _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
