On Jun 24, 2007, at 11:54 AM, ian wrote: > Of course, for an "editor" widget, we *might* force a fixed-pitch > font, > then obviate the need to measure at all at run-time - but that's not > really what people want from a generic Text_Display widget...
The only thing I can see is to create some kind of hash table for reoccurring strings. That way we could avoid recalculating the width of the same text fragments in static labels over and over, and even the text editor could benefit greatly from this. The hashing itself should be fast. > Also - at a tangent - do we want to consider making the font ID code > more than a uchar for a 1.1.x-utf8 port, now that many machines have > more than 256 fonts installed? Absolutely. The font number must be a 32bit integer pointing into a self-expanding array. There are a few other spots wher this applies, like box types (ok, maybe 16bit are enough here) and symbols. ---- http://robowerk.com/ _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
