X and Fluxbox :: Fluxbox keybinding not loading

I didn't specifically reload the configuration, I rebooted the whole enchelada. But I found the reconfigure the window manager button in the menu but that dina du it neither. Hey, I just noticed that my light bulb is lit up. Well, it's just a freakish spike...I assure you I have no bright ideas on this one.

Well.....that kicks me in the pants....

Do the other keybinds work?
Try Alt+Tab to switch between windows and Alt+F1/F2 to switch desktops.

OK, so now when I go back and use xev to identify keycodes I get something a little different. Number 8 on the keyboard is the one that I changed in the keys file like so...

Code Sample

none 8 :NextTab

It now show in xev as:

Quote

FocusOut event.serial 20, synthetic NO. window 0xa00001,
mode NotifyGrab, detail NotifyAncestor

FocusIn event.serial 20, synthetic NO. window 0xa00001,
mode NotifyUngrab, detail NotifyAncestor

KeymapNotify event. serial 20, synthetic NO, window 0x0,
keys 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

The rest of the numbers that have not been modified all give something like this "9" does:

Quote

KeyPress event. serial 20, synthetic NO, window 0x1a00001,
root 0x33, subw 0x1a00002, time 1927327932, (44,37), root:(636,84),
state 0x0, keycode 18 (keysym 0x39, 9), same_screen YES
XLookupString gives 1 bytes: "9"

KeyRelease event. serial 20, synthetic NO, window 0x1a00001,
root 0x33, subw 0x1a00002, time 1927328014, (44,37), root:(636,84),
state 0x0, keycode 18 (keysym 0x39, 9), same_screen YES
XLookupString gives 1 bytes: "9"

Which is the format that the "8" showed before I edited. So something changed. Anyone care to back me up on syntax? I'm going to try the keycode instead of the name...will post.

The fluxbox documentation shows using the name, the keycode didn't work. I did however successfully map an xmms command to a key in the form of "None 8 :ExecCommand xmms -p". But I still need to be able to use the mapping in x such as NextTab. Ideas? Thoughts? Comments?

If you map a key with no modifier fluxbox grabs that key, so it is not passed to applications. This is why the xev display is unusual....it knows something was pressed but does not receive anything specific.

Only thing I can think of at the moment is maybe you have numlock off. This might prevent the keypad keys from properly registering. Fluxbox might be seeing the keypress as KP_Home instead of KP_7.

FYI you probably don't want to map something like "none 8". Fluxbox will grab it every time and you won't be able to type '8' in an application. As a rule I don't map any standard keys without using a modifier.

Next Page...
original here.