nanogui: Re: FLTK font question
Subject:
Re: [nanogui] FLTK font question
From:
"Greg Haerr" ####@####.####
Date:
7 Jul 2011 19:24:52 -0000
Message-Id: <2E80906F876B49FAB37670D28BB21BF7@winXP>
> with fltk1110 there is first a xlistfonts call with
> "-*-helvetica-bold-o-normal--*" which is returned with NULL by NXLIB. Then
> fltk1110 makes a xloadfont call for the fixed font, assuming that this is
> always present.
> fltk130, however, calls xlistfonts again with the pattern "fixed". NXLIB
> again does not find that font and returns NULL. Then fltk130 continues
> without text to the screen.
> Do you have a suggestion how I can make it find the fixed font with an
> xlistfonts call?
In older versions of NXLIB, an xlistfonts call for "fixed" resulted
in a specially-cased return of the microwindows fixed system font.
This was found to cause problems in other Xlib applications, so it
was removed.
In the 0.47dev version of NXLIB, we've added the capability
to alias a requested font with a filename or XLFD font specification.
The fonts.alias file performs this function. Just like it's Linux
counterpart,
it lists aliases on each line with ! used a comments. Thus, to
alias "fixed" the following lines could be used:
! fonts.alias file
fixed -misc-fixed-medium-r-semicondensed--13-120-75-75-c-60-iso8859-1
In addition, -*- can be used for wildcards, as xlistfonts basically recurses
using the new value. It also works for scaled fonts.
> At the end of the day I have to get NXLIB to find the truetype fonts
> though - agreed.
This can be done simply by loading truetype font directories (including
fonts.dir
files) from an X11 distribution into your working directory.
Regards,
Greg
----- Original Message -----
From: Ricardo Jasinski
To: Georg Potthast
Sent: Friday, July 01, 2011 2:03 AM
Subject: Re: [nanogui] FLTK keyboard question
Hi Georg,
this is what we use (it is for FLTK 2.0 though):
/fonts # ls -la
drwxr-xr-x 2 0 Sep 21 2010 .
drwxr-xr-x 7 0 Sep 21 2010 ..
-rw-r--r-- 1 495680 Sep 21 2010 DejaVuLGCSans.ttf
-rw-r--r-- 1 406456 Sep 21 2010 DejaVuLGCSansCondensed-Bold.ttf
lrwxrwxrwx 1 17 Sep 21 2010 dejavulgcsans.ttf ->
DejaVuLGCSans.ttf
lrwxrwxrwx 1 31 Sep 21 2010 dejavulgcsanscondensedbold.ttf ->
DejaVuLGCSansCondensed-Bold.ttf
-rw-r--r-- 1 171 Sep 21 2010 fonts.dir
/fonts # cat fonts.dir
2
dejavulgcsanscondensedbold.ttf -dejavu-DejaVuLGCSans-medium-r-bold--0-0-0-0-p-0-iso8859-1
dejavulgcsans.ttf -dejavu-DejaVuLGCSans-medium-r-normal--0-0-0-0-p-0-iso8859-1
/fonts #
Happy hacking,
Ricardo.
On Wed, Jun 29, 2011 at 2:43 AM, Georg Potthast ####@####.####
wrote:
I found that my kbd_dj driver had a bug and returned the wrong scancode
value. Now I can make keyboard input with FLTK version 1.1.10. However,
since FLTK uses the scancode, I only have a US keyboard layout. I have to
see if this can be configured in FLTK.
With version 1.3.0 I cannot tell if the keyboard works, since there is no
text displayed on the screen, even the cursor is not present.
Where can I get a populated fonts.dir file?
Georg
---------------------------------------------------------------------
To unsubscribe, e-mail: ####@####.####
For additional commands, e-mail: ####@####.####
