(edited to remove initial misdiagnosing of potential causes on my part :D )
I looked back, and had got to a similar issue in my Make Install 2wm thread before with adding Mod4, but now trying to understand why 2wm is auto-voiding Fn keys.
I'm running BBQ Break 4.2.0-trunk-586.
Once I installed 2wm on top, can't use default (keyboard printed)Fn keybindings there.
They work as described in Openbox (just rechecked). Looked in Openbox config files, but nothing there implicitly making Fn Keybindings for Openbox alone. I couldn't really see anything in 2wm's small code being able to override wherever these default key bindings are. I nano read through every 2wm file, I don't know what I'm looking at per say, but the only things with keys/keybindings are all based on a modkey of Alt, or Alt+Shift. Nothing I saw that sounded like it would override default Fn key uses...
I ran XEV and Fn3or4 show :
Code: Select all
KeyPress event, serial 32, sythetic No, window 0x3a00001,
root 0x96, subw 0x0, time 2523450, (434,557), root:(435,558),
state 0x0, keycode 123 (keysym 0x1008ff13, XF86AudioRaiseVolue), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
Recommended fixes? I'll accept Right, and/or Easy options...
Somehow add Fn shortcuts to 2wm config(or does someone know how it's non-config files kill Fn key)?
Somewhere else in base Debian files where Fn keybinds might be stored, somehow make those override all window managers?
Long search short, I have no idea what to do now, lol. I'm in over my head as usual, but I tried to do as much footwork as possible so you guys don't have to completely babysit me :D