nanogui: How to use nano-X fonts in fltk 1.1.9
Subject:
Re: [nanogui] How to use nano-X fonts in fltk 1.1.9
From:
"Greg Haerr" ####@####.####
Date:
24 Feb 2010 04:56:14 -0000
Message-Id: <01d401cab50d$87e0cf20$6564a8c0@winXP>
> it is a shame fltk 2.0 didn't work for you; I find it much more
> resourceful
than fltk 1.x and easier to use, integrate and undestand. If you haven't
done so yet, maybe you could try to compile a simple demo (one of those
bundled with the fltk distribution) to sort the errors you are finding.
I'll have to look into this. I've been playing around alot with
FLTK 1.1(.10), and making changes to NXLIB for bug
fixes and enhanced font support.
> Anyway, I think I can't help much with fltk 1.x fonts; however, there's
> one
alternative that may be suitable for you. You could change the default
nano-X system font (it is compiled-in with the nano-X server) or add many
other fonts if necessary. This would be completely fltk-independent.
I have recently updated nano-X to v0.92RC2 and NXLIB
to 0.46RC2, both in the git repository. There is one
big change that could help, which is support for the
newer X11 fonts.alias file. This file sits in the X11 font
directory like fonts.dir, and is looked first to find a listed
alias for any requested font. For instance, FLTK 1.1.10
has it's X11 font list in src/fl_fonts.cxx. By default,
FLTK asks for a long-named "-adobe-....." font,
which, in Ubuntu 9.10, is aliased to another long named
XLFD font, which ultimately is found in fonts.dir to
be... HelvR14.pcf.gz, the old-fashioned helvetica 14 point
font.
Now that NXLIB supports the fonts.alias file, this could
be used to translate fonts requested by any X11 application
automatically to installed (or core) nano-X fonts.
Regards,
Greg
