nanogui: first experiments: problems
Subject:
Re: [nanogui] first experiments: problems
From:
"Jorge Marques Pelizzoni" ####@####.####
Date:
15 Aug 2008 22:21:25 -0000
Message-Id: <63187.189.35.31.159.1218838708.squirrel@mail2.icmc.usp.br>
First of all, let me thank all of you for your very useful replies. Now
answering Greg's message specifically:
Greg Haerr wrote:
> These usually happen because the above X11 library entrypoints
> (XParseColor) aren't defined in NXLIB. The stubs.c
> file is useful in these cases. However, in this particular case,
there's a library issue, since XParseColor is implemented in
> NXLIB.
>
However, this happens when I try to use flnx, not nxlib. Where can I find
stubs.c?
> : 2 - no windows could be resized nor moved, which is possible without
nano-X;
>
> This is a nanowm window manager issue, since nano-X itself, like X11,
doesn't deal with window resize requests from the user directly.
Sorry, my bad! I didn't know nanowm even existed :o) Everything works fine
now as regards moving and resizing.
>
> The keyboard map may need to be changed in NXLIB. NXLIB
> is forced to use an X11 style scancode oriented keymap,
> which may be incorrect for your system. Make sure you're
> running TTYSCAN=Y in nano-X config.
You mean TTYKBD=Y, right? Both TTYKBD=Y and SCANKBD=Y are set. I also tried
TTYKBD=Y and SCANKBD=N. By the way, what do they mean? Are they mutually
exclusive?
Anyway, nothing worked out. How can I change the keymap? I tried modifying
nxlib/keysymdef.h to no success...
>
> : fnt_createfont:
/usr/share/fonts/X11/100dpi/helvR12-ISO8859-1.pcf.gz,0
> : not found
> : Segmentation fault
>
> Are you running a big-endian system?
Nope.
> This is likely a bug in the nano-X > PCF font subdriver. They should be
fixed in the
> CVS source version, also available as a snapshot from the ftp site.
I am using the snapshot and the problem persists. HAVE_PCFGZ_SUPPORT=Y
makes Nano-X segfault in that test case.
Thanks again for everything.
Cheers,
Jorge.
