Hello, vtpup.vtpup wrote:Pemasu, I've tried your combo xkeybindings, vattery etc .pets in this machine with various other puppies (looks like it's incorporated in this one) and the machine is unresponsive to it. Continues to ignore the bindings.
(...)
On the subject of xbindkeys, I have two experiences to share:
xbindkeys provide a low-level binding with the keyboard keys.
You can have interference from a superior level, like
from the key shortcuts you can set up with the ROX-Filer.
For example, if you have set Ctrl-A in xbindkeys to lauch
abiword and in ROX you have set Ctrl-A to launch Alsa-config,
the ROX shortcut will have precedence. Alsa-config will be launched, not abiword.
or
from the window manager, which has absolute precedence over all keybindings.
For example, jwm or icewm will steal any keybinding involving a mouse click. In other words, if you have a key binding in xbindkeys such as Ctrl+A+leftmouse click = abiword, it will be inoperative in jwm or icewm because any desktop click is transmitted to them, not to the xbindkeys program.
So, when you prepare the key conbinations in xbindkeys, make sure that
you do not have a mouse-click reference (which is handled by the window manager) and
that the key shortcut is unique (that the same shortcut does not exist in ROX-Filer).
I hope this helps your understanding of xbindkeys.
BFN.
Note. Icewm can be made NOT to control the background clicks iun the preferences file. Oroborus does not control any background click. Aewm and Echinus, only the left-mouse click (if I remember correctly). In short, you have to test with the window manager you are using.
