> I *do* hack fl_font_xft.cxx to include > fl_font_x.cxx with all the symbols renamed (via preprocessor > directives), but a second look revealed that I do so merely to address > an unrelated problem affecting programs that inadvertently mixed Xft 1 > and Xft 2. (At the time, several ITK/VTK apps triggered this, thanks > in part to VTK's wholesale inclusion[!] of Xft 1.)
OK. Can I ask why you include fl_font_x.cxx in fl_font_xft.cxx? They are "parallel" implementations as I saw it, what do you gain by using both? And is it something I should be doing? > > Anyway, if there's a perceived need for this in the XFT builds, I'll > > try and find some time to work up a better version, and > maybe a patch > > for the mainline 1.1.8 build too. > > Thanks! No worries. Just don't hold your breath waiting for me...! I might be a while. -- Ian SELEX Sensors and Airborne Systems Limited Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14 3EL A company registered in England & Wales. Company no. 02426132 ******************************************************************** This email and any attachments are confidential to the intended recipient and may also be privileged. If you are not the intended recipient please delete it from your system and notify the sender. You should not copy it or use it for any purpose nor disclose or distribute its contents to any other person. ******************************************************************** _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
