> > On my system, the XStringToKeysym() function does indeed return
> > the proper keysym value, but then XKeysymToKeycode returns zero.
> > I don't know if it's the same problem on your system.
>
> No, it isn't - the following program:
>
> === snip ===
> #include
> #include
>
> main()
> {
>
On 09 Feb 2002 13:41:36 +0100, Stanislav Meduna wrote:
>
> Umm, you was right - I did not have the keycode mapping - at the
> time of fvwm starting, that is :-( My environment starts a keyboard
> mapping application, so I see the mapping when running my test
> application, but this is of course af
Hello,
> If you want to debug this, you should
> start in the files fvwm/bindings.c and libs/Bindings.c.
Umm, you was right - I did not have the keycode mapping - at the
time of fvwm starting, that is :-( My environment starts a keyboard
mapping application, so I see the mapping when running my t
Hi,
> > That the
> > XStringToKeysym knows about them is something buried in the
> > Xlib - the manpage says that this behaviour is implementation
> > dependent.
>
> Which man page?
XStringToKeysym and related:
Standard KeySym names are obtained from
by removing the XK_ prefix fr
Hello,
> On my system, the XStringToKeysym() function does indeed return
> the proper keysym value, but then XKeysymToKeycode returns zero.
> I don't know if it's the same problem on your system.
No, it isn't - the following program:
=== snip ===
#include
#include
main()
{
Display *d = XOpe
This reply is from Dominik Vogt, because of mail system problems,
the reply appears to come from me. If you'd like to reply,
reply to fvwm-workers.
On Thu, Feb 07, 2002 at 06:34:02AM -0600, fvwm-bug wrote:
> FVWM Bug Tracking notification
>
> new message incoming/852
>
> Full_Name: Stanislav Me
FVWM Bug Tracking notification
new message incoming/852
Message summary for PR#852
From: [EMAIL PROTECTED]
Subject: Keysyms for special keys are not recognized
Date: Thu, 07 Feb 2002 06:34:01 -0600
0 replies 0 followups
> ORIGINAL MESSAGE FOLLOWS <
