nanogui: Re: FLTK font question
Subject:
Re: [nanogui] FLTK font question
From:
"Greg Haerr" ####@####.####
Date:
29 Jul 2011 23:23:47 -0000
Message-Id: <DCABB55A46234F2D87952F7A9BF1E8F6@winXP>
Georg -
I've fixed XLoadFont and XListFonts in NXLIB and
everything should now work for you. I've tested with
FLTK 1.1.10 and 1.3.0, and fixed the following issues:
o fix XLoadFont special case handling of 'fixed' -> uses mwin SystemFixed
o add XListFonts handling of 'fixed', allows FLTK 1.3.0 to work
o add fonts.alias handling in XListFonts
o allow spaces in filenames (was actually a tab bug in line reading routine)
o allow fonts.alias aliasing to non-XLFD fonts
Please pull down the nxlib-src snapshot or cvs, and check
that everything works for you. You should not have to
modify any code in FLTK 1.3.0, just use fonts.alias files.
Regards,
Greg
: I changed my fonts.alias file to this:
:
!-*-helvetica-medium-r-normal--* -misc-dejavu_sans-medium-r-normal--0-0-0-0-p-0-ascii-0
: fixed -misc-dejavu_sans-medium-r-normal--0-0-0-0-p-0-ascii-0
: Fixed -misc-dejavu_sans-medium-r-normal--0-0-0-0-p-0-ascii-0
:
: This did also not work as you can see far below. I had already found and
: reported in the past that NXlib does not return the same response as Xlib
: when called "font_enumfonts - pattern: fixed" which causes FLTK 1.3.0 to
: give up. The old FLTK version did not make a call font_enumfonts on fixed
: but assumed that to be present. This resulted in the compiled-in font of
: nano-x being used, however, one had only a one size font then.
:
: As you wrote it should also work with a fonts.alias file and that would
: avoid a change in the FLTK code. That is what I was trying to get to work
: now.
:
: Georg
