It may be a good idea to figure out why this is so slow. Apparently *drawing* the text is reasonable, it is only the measurement that is slow? That implies this can be fixed somehow.
The fltk2.0 drawing code scrapped all uses of "measure 1 character", and instead has a function to get the width of a block of UTF-8. It was not hard to make the text editor use this only. On 01/24/2011 09:28 AM, Matthias Melcher wrote: > > On 24.01.2011, at 17:50, Michael Sweet wrote: > >> Unicode isn't 16-bits - you need to allow for 20-bits. > > He allows for 20 bits, but only caches the character width of the first 65536 > characters. Maybe a hashing scheme could be used? _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
