> > The Quartz port works all the way. The only drawback is the window > > code that still uses old-style windows and requires converting a > > Quickdraw drawable into a Quartz drawable. Other than that, Quartz > > works very well for me.
OK, I got a quick shot at trying the Quartz port and it does indeed work as advertised - although I have a sense that it may be a little slower to finish the first window than the QD variant? I guess that's an artefact of the Quartz/QD mapping or something...? Anyway, I've bodged around with that a bit and got it rendering Unicode text now, kinda, more or less... the editor demo can display my UTF-8 test doc for example. But... there are a few "features" that need to be resolved still. Basically, it's as buggy as... (indeed, the *nix and win32 ports need some work too FWIW.) So, a few questions - do we know where the unicode support code in fltk-2 came from? Is it OK to just use it? (I'm thinking of utf.c mainly here, and posisbly the X-windows stuff) as there might be some scope for merging that with the fltk-1.1-utf code to tidy up a few things that are bothering me. -- Ian _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
